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 commands/lindoelio/spec-driven-steroids/inject-guidelines.commandgit clone --depth 1 https://github.com/lindoelio/spec-driven-steroidsWrote 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/commands/lindoelio/spec-driven-steroids/inject-guidelines.command)<a href="https://agentmods.dev/commands/lindoelio/spec-driven-steroids/inject-guidelines.command"><img src="https://agentmods.dev/badge/commands/lindoelio/spec-driven-steroids/inject-guidelines.command.svg" alt="Measured on agentmods" 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 | $0.00046 | $0.00505 |
| Opus 5 | $0.00023 | $0.00253 |
| Sonnet 5 | $0.00009 | $0.00101 |
| Haiku 4.5 | $0.00005 | $0.00051 |
Grade A, and why
inject-guidelines.command 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 4d 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 — 56 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are Spec-Driven Steroids Guidelines Injector. Analyze this repository and generate or update the standard guideline documents with a consistent, low-friction workflow.
Workflow
Step 1: Repository Analysis
- Inspect existing guideline files first to avoid duplication.
- Select representative files across config, source, docs, and tests.
- Return the repository-analysis output expected by the skill.
Step 2: Repository Insights
- Analyze the selected files for stack, structure, conventions, documentation coverage, and conflicts.
- Determine whether the repository's testing strategy is clear or mixed.
- If testing strategy is unclear or mixed, default generated
TESTING.mdto Testing Trophy guidance. - Under that fallback, prefer integration tests as the main confidence layer, e2e tests for critical user journeys, and unit tests as secondary and selective.
- Return the repository-insights output expected by the skill.
Step 3: Existing Files Decision
- Default existing guideline files to managed-section updates.
- Ask the user only when a whole-file overwrite or explicit skip decision is genuinely needed.
- Missing guideline files must be created automatically.
- Do not treat missing guideline files as optional.
Step 4: Document Generation And Writing
- Generate these six documents by default:
AGENTS.mdCONTRIBUTING.mdSTYLEGUIDE.mdTESTING.mdARCHITECTURE.mdSECURITY.md
- Use the Document Responsibility Matrix from the skill.
- Preserve user-authored content outside managed sections when updating.
- Write the files before asking the user to review the result.
Key Behaviors
- Generate all six guideline documents by default unless the user explicitly skips named files.
- Default existing guideline files to managed-section updates unless the user asks for overwrite or skip behavior.
- Use managed section markers for generated content.
- Cross-reference related docs instead of duplicating guidance.
- Keep behavior aligned with the
project-guidelines-writerskill rather than adding platform-specific workflow rules.
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.
- 4d ago First seen · 56 lines · 46 tokens per session scan A bae817360453
inject-guidelines.command is a command published in the GitHub repository lindoelio/spec-driven-steroids (54 stars, last pushed 25d ago), licensed MIT. It adds 46 tokens to every session and 505 once invoked, about $0.0002 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-30.
Other commands, from other repositories
archive
Archive a feature specification into main project memory after merge, resolving gaps and conflicts.
audit
Audit a file, directory, or whole repo for insecure default configuration: fallback secrets, default credentials, fail-open switches, weak crypto, permissive access, debug leakage. Parallel sweeps collect candidates, then a refuting verifier traces each one to the security decision it reaches before it is reported.
compact
Compact one or more Spec-Driven Development artifacts in place to reduce token cost on subsequent /speckit. commands. Lossless on requirements, decisions, contracts, IDs; strips template scaffolding, examples, and prose padding. The original is preserved as .full.md the first time an artifact is compacted.
concise
Toggle a project-local concise-output directive that suppresses agent prose padding during SDD steps. State lives in the project's agent memory file (AGENTS.md preferred when present, else CLAUDE.md / GEMINI.md / .cursor/rules / .windsurf/rules / etc.) inside a clearly marked block, so it is reversible and reviewable.
restore
Restore one or more Spec-Driven Development artifacts to their original (pre-compaction) state from the .full.md backups created by /compact. Deletes each backup after a successful restore.
scope
Build a focused reading manifest for the next workflow step. Names the files the agent should load, the sections it can skip, and the running token budget. Run this before /speckit.plan, /speckit.tasks, or /speckit.implement to keep their working context lean.