Testing & Security skills

Autonomous driver loop for ExploitHunter vulnerability-research campaigns. Runs breadth-first waves of research lanes on rented hosts with no per-request human approval, steers lanes via the shared Investigation Graph (demoting dead ends, respawning on high-signal priorities), saturates host capacity, and enforces wave/budget/safety discipline. Use when driving a multi-target bug-hunting campaign, launching parallel research lanes, or resuming a campaign from a state snapshot.

The English summary is being prepared. Showing the original description.

Passive code-review lane for authorized repositories, local checkouts, uploaded source archives, and diffs. Use when the security research agent needs deterministic candidate discovery before expensive AI investigation, scoped PR-style review, append-only evidence records, or independent revalidation of code findings.

The English summary is being prepared. Showing the original description.

Test-driven development with red-green-refactor loop. Use when user wants to build features or fix bugs using TDD, mentions "red-green-refactor", wants integration tests, or asks for test-first development.

The English summary is being prepared. Showing the original description.

Offload builds, tests, or artifact verification to authorized SSH hosts and isolated worktrees; synchronize remote fixes into dedicated coordinator commits and preserve reproducible build provenance. Use for spare development capacity and remote build troubleshooting. Paid provisioning requires a separate resource lifecycle contract.

The English summary is being prepared. Showing the original description.

Passive, citation-grounded review of security-relevant specifications, protocols, standards, APIs, and implementations. Use when a reviewer must trace external preconditions and invariants into source code without treating a cited claim as proof of a vulnerability.

The English summary is being prepared. Showing the original description.

Turn a specific vulnerability, patch, CVE, Version Diff, or Changelog Claim into a proactive security exploration plan. Use when the user wants research angles, lateral target discovery, patch/CVE strategy, new surface discovery, or hypothesis generation from vulnerability intelligence.

The English summary is being prepared. Showing the original description.

Select established CTF and security-research tools for authorized artifact triage, web inspection, reversing, crypto, forensics, networking, and exploit validation. Use when a user provides a CTF-style tool catalog, asks which tools to use, or needs safe usage instructions for common offensive/security tools.

The English summary is being prepared. Showing the original description.

Plan vulnerability research using conventional bug-hunting and pentest stage names, specialty playbooks, and a research-hypothesis-experiment loop. Use when designing a bug bounty workflow, selecting tools and strategies, building a decision tree, or turning a target/scope into a staged hunting plan.

The English summary is being prepared. Showing the original description.

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

The English summary is being prepared. Showing the original description.

Up-to-date Zig programming language patterns for version 0.17.0-dev (0.16.0 stable APIs plus the 0.17 deltas). Use when writing, reviewing, or debugging Zig code, working with build.zig and build.zig.zon files, or using comptime metaprogramming. Critical for avoiding outdated patterns from training data - especially std.net→std.Io.net (requires Io instance), std.time timestamps removed (use clock_gettime), std.Thread.Mutex/Condition/sleep removed (use pthreads), std.crypto.random removed, build system APIs (root_module, Compile methods→Module methods), I/O APIs (buffered writer pattern), container initialization (.empty/.init), allocator selection (DebugAllocator), ArrayList now unmanaged by default, @typeInfo lowercase fields (.@"struct" not .Struct), and removed language features (async/await, usingnamespace). Also covers 0.17.0-dev deltas: b.args→run_cmd.addPassthruArgs(), std.gpu→std.spirv, @bitCast logical-bit (endian-agnostic) semantics, build configurer/maker split, and the zig-pkg/ package directory. Also covers quality tooling Zig does not ship: coverage with kcov (and why in-file tests wreck the denominator), detecting unused private functions (neither the compiler nor zlint's unused-decls finds them), duplicate detection with jscpd, zlint (NOT the same-named X.509 linter in Homebrew), and the built-in fuzzer whose testOne now takes *std.testing.Smith rather than []const u8.

The English summary is being prepared. Showing the original description.

Disciplined diagnosis loop for hard bugs and performance regressions. Reproduce → minimise → hypothesise → instrument → fix → regression-test. Use when user says "diagnose this" / "debug this", reports a bug, says something is broken/throwing/failing, or describes a performance regression.

The English summary is being prepared. Showing the original description.

Pragmatic testing guidance focused on confidence, behavior over implementation details, and integration-first coverage. Use when designing a test strategy, writing or reviewing tests, reducing brittle mocks, or deciding what is worth testing in an application or library.

The English summary is being prepared. Showing the original description.

End-to-end smoke against the local rembric dev server (`pnpm run dev`, host Next.js dev on :3000). Apply when the user says "smoke", "probar contra docker", "dev:up", or after applying an OpenSpec change that touches HTTP (`apps/web/src/app/api/`), MCP tools (`packages/mcp/src/`), or DB migrations (`packages/db/src/migrations/`). Encodes bring-up, readiness verification, probe pattern and teardown — not the probes themselves.

The English summary is being prepared. Showing the original description.

Review the current branch for bugs, intent fit, and test coverage; run or write tests; commit focused work; open or update a PR.

The English summary is being prepared. Showing the original description.

Create and scaffold plugin directories for Codex with a required `.codex-plugin/plugin.json`, optional plugin folders/files, and baseline placeholders you can edit before publishing or testing. Use when Codex needs to create a new local plugin, add optional plugin structure, or generate or update repo-root `.agents/plugins/marketplace.json` entries for plugin ordering and availability metadata.

The English summary is being prepared. Showing the original description.

The Rembric TUI installer contract — the single, canonical install/setup/upgrade/uninstall path (`apps/plugin/install.sh`, fronted by the repo-root `install.sh` shim). Apply when touching `install.sh`, the root shim, any per-client `install.sh`/`uninstall.sh`, `marketplace.json`, or distribution docs (README, `docs/agents.md`, plugin/client READMEs). Covers the orchestrator model, what must not break, and where the source of truth lives. For running the validation suite, use `rembric-tui-installer-e2e`.

The English summary is being prepared. Showing the original description.

Apply when creating, modifying, or reviewing any Rembric agent plugin. Triggers on changes under `apps/plugin/`, on new clients added alongside Claude Code / Codex CLI / Hermes Agent / opencode / Pi, on edits to `apps/plugin/mcp-bridge/`, `apps/plugin/bin/rembric-plugin-core.mjs`, per-client manifest changes, or plugin install/uninstall scripts. End-to-end validation against a local dev server (`pnpm run dev`, host Next.js on :3000) is mandatory whenever local testing is feasible.

The English summary is being prepared. Showing the original description.

Runnable end-to-end validation playbook for the Rembric TUI installer — catch breakage before merging/deploying, AND a sandboxed manual walkthrough to evaluate/iterate its UI/UX without polluting your real env. Apply before shipping any change touching `apps/plugin/install.sh`, the repo-root `install.sh` shim, any per-client `install.sh`/`uninstall.sh`, or distribution docs, or when you want to preview/try/demo the installer and polish how it looks and feels. Layered: CI-safe headless (vitest + `sh -n`), local install round-trips, operator interactive pty smoke, an optional full Docker `up` smoke, plus a sandboxed manual UX walkthrough. For the installer contract/what-not-to-break, see `rembric-tui-installer`.

The English summary is being prepared. Showing the original description.

Apply npm/pnpm supply-chain hardening when adding a dependency, editing package.json/.npmrc/pnpm-workspace.yaml, reviewing a lockfile change, or configuring CI install steps. Covers the 17 practices from lirantal/npm-security-best-practices.

The English summary is being prepared. Showing the original description.

If CGM is not available, continue monitoring blood glucose with point-of-care testing as an alternative option. Trigger phrases include: "CGM is not available, what should we use for glucose monitoring?

The English summary is being prepared. Showing the original description.

Evaluates basal insulin rates through basal rate testing across different time periods and adjusts as indicated. Triggered by clinician orders to 'Perform basal rate test to verify pump settings' or 'Check basal rates during periodic pump review'.

The English summary is being prepared. Showing the original description.

Recommends real-time CGM with confirmatory bedside POC-BG monitoring for insulin dosing adjustments rather than POC-BG testing alone in adults with insulin-treated diabetes at high risk of hypoglycemia. Consider this approach for patients aged ≥65 years, BMI ≤27 kg/m², total daily insulin dose ≥0.6 units/kg, CKD stage ≥3, or recent hypoglycemia.

The English summary is being prepared. Showing the original description.

This skill recommends against initiating cortisol-lowering treatment when there is no established diagnosis of Cushing's syndrome. It is triggered when a clinician considers treating suspected CS based only on borderline biochemical abnormalities or nonspecific signs without confirmatory testing; examples include "suspected CS", "borderline UFC", "no confirmed diagnosis", "consider empiric ketoconazole".

The English summary is being prepared. Showing the original description.

This skill recommends using biochemical tests to screen for hypercortisolism to detect recurrence in patients with ACTH-dependent Cushing's syndrome after surgical remission. It is triggered during postoperative follow-up when the HPA axis has recovered, annually, or sooner if clinical signs of hypercortisolism (e.g., weight gain, hypertension, glucose intolerance) or abnormal late-night salivary cortisol/UFC appear.

The English summary is being prepared. Showing the original description.