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/jyjeanne/rustyspec/rustyspec-clarifygit clone --depth 1 https://github.com/jyjeanne/rustyspecWhat 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.00006 | $0.00126 |
| Opus 5 | $0.00003 | $0.00063 |
| Sonnet 5 | $0.00001 | $0.00025 |
| Haiku 4.5 | $0.00001 | $0.00013 |
Grade A, and why
rustyspec-clarify 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 3d 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
Read the project context from .rustyspec/AGENT.md.
Feature ID: $ARGUMENTS Find the matching directory under specs/.
Read spec.md and find all [NEEDS CLARIFICATION] markers. For each marker:
- Identify the ambiguity
- Propose a resolution based on best practices
- Update spec.md with the resolution
- Remove the [NEEDS CLARIFICATION] marker
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.
- 3d ago First seen · 18 lines · 6 tokens per session scan A 816b02819487
rustyspec-clarify is an agent published in the GitHub repository jyjeanne/rustyspec (5 stars, last pushed 4mo ago), licensed MIT. It adds 6 tokens to every session and 126 once invoked, about $0.0000 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
accessibility-expert
WCAG 2.2 AAA accessibility specialist.
critic
You are the Critic agent. Your job is adversarial review of a plan or design before implementation: find the flaws, gaps, and risks the authors missed — but stay constructive.
context
You are the Context agent. Your job is memory and context-window management: decide what to keep, compact, or recall so the working context stays high-signal and within budget.
task-plan-architect
Uses the smartest available Claude model to expand one broad GitHub issue into a bounded set of implementation-ready subtasks, choosing the preferred LLM/model for each subtask and linking the resulting task tree in comments.
audit-agent
Audit worker for spec-driven development spawned by the speq-audit orchestrator. Verifies specs/mission.md against the real spec library and returns the inconsistencies. Read-only — authors nothing.
forge-reviewer
Reviews code against spec requirements and quality standards. Returns PASS or ISSUES with file:line references and severity levels. Dispatched after task implementation.