Borrowing it
Nothing to install: this file belongs to jyjeanne/rustyspec. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/jyjeanne/rustyspec/master/.github/agents/rustyspec-specify.agent.mdgit clone --depth 1 https://github.com/jyjeanne/rustyspecWrote 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/agents/jyjeanne/rustyspec/rustyspec-specify)<a href="https://agentmods.dev/agents/jyjeanne/rustyspec/rustyspec-specify"><img src="https://agentmods.dev/badge/agents/jyjeanne/rustyspec/rustyspec-specify/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/agents/jyjeanne/rustyspec/rustyspec-specify"><img src="https://agentmods.dev/badge/agents/jyjeanne/rustyspec/rustyspec-specify.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.00005 | $0.00182 |
| Opus 5.5 | $0.00002 | $0.00073 |
| Sonnet 5.5 | $0.00001 | $0.00036 |
| Haiku 4.5 | $0.00001 | $0.00018 |
Grade A, and why
rustyspec-specify 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 1mo 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/ (e.g. specs/001-feature-name/).
Fill in the feature's spec.md with real content:
- Replace [Brief Title] with a descriptive story title
- Write user stories with clear Given/When/Then acceptance scenarios
- Define functional requirements (FR-001, FR-002, etc.)
- Identify key entities and their relationships
- Define measurable success criteria
- List edge cases
Keep requirements technology-agnostic. Focus on WHAT, not HOW. Only edit the existing spec.md — do not create new files.
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.
- 1mo ago First seen · 22 lines · 5 tokens per session scan A 48e4f7819100
rustyspec-specify is an agent published in the GitHub repository jyjeanne/rustyspec (5 stars, last pushed 6mo ago), licensed MIT. It adds 5 tokens to every session and 182 once invoked, about $0.0000 per session on Opus 5.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
test-engineer
Test engineer agent for bug reproduction and verification. Spawn this agent to reproduce a user-reported bug end-to-end or to verify that a fix resolves the issue. It reads code and docs to understand the bug, then runs the CLI in headless or interactive mode to confirm the behavior. It can write test scripts as a…
scramjet:command-architect
Use when creating or substantially redesigning Scramjet commands or command sets.
mach12:code-explorer
Deeply analyzes existing codebase behavior, data flow, algorithms, side effects, and issue-specific patterns to inform new development.
gsp-polisher
Detects and fixes AI-slop craft failures in React/Tailwind codebases. Spawned by /gsp-polish.
gsp-brand-auditor
Audits existing brand identities for evolution. Spawned by /gsp-brand-audit.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.