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 skills add lindoelio/spec-driven-steroids --skill spec-driven-brief-plannergit 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/skills/lindoelio/spec-driven-steroids/spec-driven-brief-planner)<a href="https://agentmods.dev/skills/lindoelio/spec-driven-steroids/spec-driven-brief-planner"><img src="https://agentmods.dev/badge/skills/lindoelio/spec-driven-steroids/spec-driven-brief-planner/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/skills/lindoelio/spec-driven-steroids/spec-driven-brief-planner"><img src="https://agentmods.dev/badge/skills/lindoelio/spec-driven-steroids/spec-driven-brief-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 99 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00067 | $0.01122 |
| Opus 5 | $0.00034 | $0.00561 |
| Sonnet 5 | $0.00013 | $0.00224 |
| Haiku 4.5 | $0.00007 | $0.00112 |
Grade A, and why
spec-driven-brief-planner 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 9d 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Spec-Driven Brief Planner
Use one compact artifact and one approval for changes that do not require the full requirements, design, and tasks lifecycle.
Contract
- Write
.specs/changes/<slug>/brief.mdbefore implementation. - Do not write implementation code until the user explicitly approves the brief.
- Do not create
requirements.md,design.md, ortasks.mdin the brief lane. - If full-lane risk appears, stop and escalate before continuing.
Full-Lane Escalation
Escalate when any condition is true:
- security, authentication, authorization, privacy, secrets, or compliance changes
- persisted data, schema, migration, or persisted-format changes
- public API, external contract, wire-format, or backward-compatibility changes
- architecture changes across packages, services, or runtime boundaries
- new production dependency, deployment, rollback, or infrastructure work
- critical concurrency, availability, or performance behavior
- more than 5 requirements or more than 8 implementation tasks
Planning Workflow
- Propose a short URL-friendly slug.
- Read only repository guidance relevant to this change.
- Inspect targeted existing code before naming files or verification commands.
- Work inline by default. Use at most one explore sub-agent only when the investigation would otherwise require more than three independent searches. Do not repeat delegated searches.
- Write
.specs/changes/<slug>/brief.mdusing the exact format below. - Run
sds validate structure <slug>andsds validate brief .specs/changes/<slug>/brief.md. - Fix validation failures and re-run both commands.
- Stop and ask:
Verdict: PASS. Approve brief <slug> for implementation?
Brief Format
# Change Brief
**Lane:** brief
## Intent
<problem, expected outcome, and scope boundary>
## Non-Goals
- <explicitly excluded behavior>
## Acceptance Criteria
- REQ-1: <observable outcome>
- REQ-2: <observable outcome>
## Repository Evidence
- Existing: `path/to/file.ts` - <evidence and role in the change>
- New: `path/to/test.ts` - <planned role>
## Implementation Plan
- [ ] 1. <concrete action>
- Change: <exact scoped change>
- Files: `path/to/file.ts`
- Verify: `focused command or observable check`
- _Implements: REQ-1_
## Risks
- <optional low or medium risk>
## Final Verification
- `final command or observable check`
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.
- 9d ago First seen · 146 lines · 0 tokens per session scan A 6bbb1cdb6d8c
spec-driven-brief-planner is a skill published in the GitHub repository lindoelio/spec-driven-steroids (54 stars, last pushed 1mo ago), licensed MIT. It adds 67 tokens to every session and 1,122 once invoked, about $0.0003 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 skills, from other repositories
artifact-conventions
Defines preservation, format, and section rules for SDD specification artifacts (spec.md, plan.md, tasks.md, checklists). Use when editing feature-artifact files under specs/ / to prevent accidental corruption of cross-referenced IDs, priorities, and gating state.
plan-authoring
Reference material for writing implementation plans (technical context, architecture decisions, data models, API contracts, project-instructions alignment). Loaded on demand by plan-feature; not directly invokable.
task-generation
Reference material with the canonical task-format grammar and decomposition rules for plan-to-tasks expansion. Loaded on demand by generate-tasks; not directly invokable.
adr-authoring
Defines the canonical MADR format, lifecycle rules, numbering policy, and SAD catalog contract for standalone ADRs under specs/adrs/.
implementation-standards
Reference material with coding standards (defensive coding, error handling, testing patterns). Loaded on demand by the Developer sub-agent (.github/agents/developer.md); not directly invokable.
spec-authoring
Reference material for writing product, technical, and operational specifications (work-item priorities, requirement families, success criteria). Loaded on demand by specify-feature; not directly invokable.