Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add dkstm95/hope --skill toxic-reviewgit clone --depth 1 https://github.com/dkstm95/hopeWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/dkstm95/hope/toxic-review)<a href="https://agentmods.dev/skills/dkstm95/hope/toxic-review"><img src="https://agentmods.dev/badge/skills/dkstm95/hope/toxic-review/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/dkstm95/hope/toxic-review"><img src="https://agentmods.dev/badge/skills/dkstm95/hope/toxic-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00025 | $0.00637 |
| Opus 5 | $0.00013 | $0.00318 |
| Sonnet 5 | $0.00005 | $0.00127 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
toxic-review scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 66 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hope Toxic Review
Coordinate independent red reviewers, verify consequential findings with blue reviewers, and adjudicate one evidence snapshot. The active session coordinates and judges; it does not serve as a reviewer or verifier.
Read ../write/references/writing-standard.md for user-facing language.
Bind the review and assign red roles
State the target, stage, material risks, evidence, exclusions, and unavailable evidence. Use the smallest role set covering distinct risks; one role is valid.
Give each role a fresh subagent with no inherited conversation. Supply only the exact target, assigned risks, direct evidence, exclusions, expected output, and absolute Skill path. Exclude earlier reasoning, drafts, implementation narrative, prior conclusions, and other reviewers' work. Separate parallel or sequential contexts are independent; repeated prompts in one context are not.
Tell red reviewers to read references/red-review.md and the shared Write
standard. Assign references/causal-review.md to one role only when the target
makes or relies on a material causal claim.
If a fresh reviewer is unavailable, explain the missing capability and stop the independent review without claiming it was performed.
Verify consequential findings
Seal red findings before verification. A candidate requires a fresh blue verifier if it alleges a high-priority defect, could block release, proposes broad, costly, destructive, or difficult-to-reverse action, or has materially incomplete, ambiguous, or uncertain evidence, scope, or impact. Confidence and review size do not waive this requirement.
Give blue only the target, scoped evidence, sealed candidates, exclusions,
expected output, and Skill path. Tell it to read references/verification.md
and the Write standard. One verifier may cover related findings; add roles
only for distinct expertise. If required verification is unavailable, identify
the unresolved candidates and stop before presenting them as adjudicated.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 2d ago Changed · -49 lines · -2 tokens per session 76b3a9bb7eaa
- 9d ago First seen · 115 lines · 27 tokens per session scan A 5f1b377b1c66
toxic-review is a skill published in the GitHub repository dkstm95/hope (8 stars, last pushed yesterday), licensed MIT. It adds 25 tokens to every session and 637 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other skills, from other repositories
figma-design-system-to-design-md
Figma design system to design.md — Extract Figma design system into a structured design.md. Use when user says 'generate design.md', 'extract design system', 'design tokens to markdown', 'create design doc from Figma', 'Figma design system to design.md', or wants to document their design system from token files and…
claude-code-session-broker
Use when running Arcgentic V2 in Claude Code and fixed Planner, Developer, and Auditor role sessions must be coordinated through a broker.
arcgentic
Use when the user says Arcgentic, asks to use Arcgentic, or wants an idea taken through a complete plan → development → self-audit → external audit workflow in Codex.
verify-gates
Runs the mechanical quality gates that the arcgentic state machine requires for state transitions. Invoked indirectly by transition.sh OR directly by orchestrator agent before declaring a state transition. Use when about to call transition.sh OR when manually verifying that a round artifact meets the gate criteria.…
session-mode
Use when a project has not yet stored session mode, when a user asks for complete arcgentic workflow execution, or when role identity handoff prompts are needed.
cross-session-handoff
Read, write, snapshot, and lock .arcgentic/state.yaml across planner, dev, audit, and optional test sessions.