Borrowing it
Nothing to install: this file belongs to PedroMosquera/squadai. 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/PedroMosquera/squadai/main/.agents/skills/sdd-propose/SKILL.mdgit clone --depth 1 https://github.com/PedroMosquera/squadaiWrote 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/pedromosquera/squadai/sdd-propose)<a href="https://agentmods.dev/skills/pedromosquera/squadai/sdd-propose"><img src="https://agentmods.dev/badge/skills/pedromosquera/squadai/sdd-propose/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/pedromosquera/squadai/sdd-propose"><img src="https://agentmods.dev/badge/skills/pedromosquera/squadai/sdd-propose.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.00015 | $0.00580 |
| Opus 5.5 | $0.00006 | $0.00232 |
| Sonnet 5.5 | $0.00003 | $0.00116 |
| Haiku 4.5 | $0.00002 | $0.00058 |
Grade A, and why
sdd-propose 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 16d 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
SDD Propose Skill
Generate and evaluate solution options before committing to a design. This skill produces a tradeoff table that the team can use to choose the best approach.
Steps
-
Review the exploration report: Understand constraints and context.
- What must not change (API contracts, data formats)?
- What are the performance/security requirements?
- What areas of the codebase will be affected?
-
Generate 2-4 solution options: Propose meaningfully different approaches.
- Option 1: Minimal change (least disruption, may be limited)
- Option 2: Standard approach (industry-standard pattern)
- Option 3: Clean-slate (ideal design, higher effort)
- Option 4 (optional): Hybrid or incremental migration
-
Evaluate each option: Analyze tradeoffs honestly. For each option, assess:
- Effort: person-hours or story points
- Risk: probability and severity of breaking changes
- Reversibility: how hard is it to undo if it goes wrong?
- Testability: how easily can this be tested?
- Maintainability: how easy to extend or modify in future?
- Alignment with constraints: does it fit all requirements?
-
Produce a recommendation: Choose one option with reasoning.
- State which option you recommend and why
- Acknowledge the main tradeoff you are accepting
- Note any blocking assumptions that must be validated first
-
List open questions: Flag anything that must be decided externally.
- Questions for the product owner (scope/priority)
- Technical unknowns requiring a spike
- Dependencies on other teams or systems
Output Format
## Proposals: <feature/change>
### Option 1: <name>
**Summary**: <one sentence description>
**Effort**: <estimate>
**Risk**: <low|medium|high> (<reason>)
**Reversibility**: <easy|hard|irreversible>
**Testability**: <easy|medium|hard>
**Pros**: <bullet list>
**Cons**: <bullet list>
### Option 2: <name>
...
### Tradeoff Table
| Option | Effort | Risk | Reversible | Testable |
|--------|--------|------|------------|---------|
| Option 1 | | | | |
| Option 2 | | | | |
### Recommendation
**Recommended**: Option <N>. <rationale in 2-3 sentences>
### Open Questions
1. <question>
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.
- 16d ago Changed a61092b45d9e
- 1mo ago First seen · 74 lines · 15 tokens per session scan A 3c08cf1aa8ca
sdd-propose is a skill published in the GitHub repository PedroMosquera/squadai (10 stars, last pushed 4d ago), licensed MIT. It adds 15 tokens to every session and 580 once invoked, about $0.0001 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 skills, from other repositories
user-research-cookiy
End-to-end user research assistant — qualitative and quantitative. Use this skill whenever the user mentions user research, user interviews, discussion guides, interview guides, research plans, qualitative research, quantitative research, user surveys, survey design, usability studies, participant recruitment…
best-practices
Transforms vague prompts into optimized Claude Code prompts. Adds verification, specific context, constraints, and proper phasing. Invoke with /best-practices.
code-documentation
Writing effective code documentation - API docs, README files, inline comments, and technical guides. Use for documenting codebases, APIs, or writing developer guides.
curate-a-team-library
Use when building a managed team skills library for a real stack. Map work to shelves, browse before curating, write meaningful whyHere notes, and create a starter pack once the first pass is solid.
audit-library-health
Use when checking the overall health of a skills library. Run doctor, validate, check for stale skills, and verify generated docs are in sync.
review-a-skill
Use when evaluating whether a skill belongs in a library. Preview content, check frontmatter, validate structure, and decide whether to keep, curate, or remove.