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 agentmods add agents/creativedswork/dscode/eval-rule-mergegit clone --depth 1 https://github.com/creativedswork/dscodeWhat 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 | $0.00016 | $0.00140 |
| Opus 5 | $0.00008 | $0.00070 |
| Sonnet 5 | $0.00003 | $0.00028 |
| Haiku 4.5 | $0.00002 | $0.00014 |
Grade A, and why
eval-rule-merge 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.
What it actually says
You are the eval semantic rule-merge worker. Compare new validated rules with existing rules and decide whether each new rule is semantically equivalent to one existing rule or should remain new. Never merge merely because categories match.
Return only the JSON array requested by the user. Cover every supplied new rule ID exactly once and reference only supplied existing rule IDs. Do not edit files, run commands, spawn other Agents, or mutate the rule store.
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 First seen · 19 lines · 16 tokens per session scan A 9474a3b7d6f1
eval-rule-merge is an agent published in the GitHub repository creativedswork/dscode (10 stars, last pushed 18d ago), licensed MIT. It adds 16 tokens to every session and 140 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 agents, from other repositories
qa-report-reviewer-agent
Auto-Harness reviewer subagent for sprint QA report compliance. Use only immediately after evaluatorqa writes the current sprint QA report.
final-report-reviewer-agent
Auto-Harness reviewer subagent for final QA report compliance. Use only immediately after evaluatorfinal writes the final QA report.
retest-report-reviewer-agent
Auto-Harness reviewer subagent for sprint retest report compliance. Use only immediately after evaluatorretest writes the current sprint retest report.
evaluator-write-qa-agent
Action-specific Auto-Harness Evaluator subagent for sprint QA. Use only when the current legal action is evaluatorqa.
evaluator-write-qa-parallel-agent
Action-specific Auto-Harness Evaluator subagent for parallel sprint QA. Use only when the current legal action is evaluatorqaparallel.
evaluator-write-retest-agent
Action-specific Auto-Harness Evaluator subagent for sprint retest. Use only when the current legal action is evaluatorretest.