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.
git 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/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/commands/lindoelio/spec-driven-steroids/inject-guidelines.command"><img src="https://agentmods.dev/badge/commands/lindoelio/spec-driven-steroids/inject-guidelines.command.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.00046 | $0.00505 |
| Opus 5.5 | $0.00018 | $0.00202 |
| Sonnet 5.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 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.
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.
- 1mo 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 today), licensed MIT. It adds 46 tokens to every session and 505 once invoked, about $0.0002 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-30.
Other commands, from other repositories
sddp-implement-qc-loop
Command description: Run implement and QC in a continuous loop. Argument hint: [optional: feature directory or branch name] Command category: orchestration Prerequisites: spec, plan, tasks.
sddp-plan
Command description: Create an implementation plan from the current feature specification. Argument hint: [optional: planning constraints or focus areas] Command category: feature-delivery Prerequisites: spec.
sddp-prd
Command description: Create or refine the canonical product document. Argument hint: [rough product idea, users, domain, or market opportunity] Command category: project-bootstrap Prerequisites: none.
sddp-qc
Command description: Run quality control against the implemented feature. Argument hint: [optional: testing focus such as unit tests, security audit, requirements sync] Command category: feature-delivery Prerequisites: spec, plan, tasks, implementation:complete.
sddp-specify
Command description: Create a feature specification from a feature description. Argument hint: [feature description] Command category: feature-delivery Prerequisites: project-instructions.
sddp-amend
Command description: Propagate a bootstrap change across canonical project artifacts and the project plan. Argument hint: [project-level change to propagate across bootstrap artifacts] Command category: project-bootstrap Prerequisites: project-instructions, product-document, technical-context, project-plan.