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-explore/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-explore)<a href="https://agentmods.dev/skills/pedromosquera/squadai/sdd-explore"><img src="https://agentmods.dev/badge/skills/pedromosquera/squadai/sdd-explore/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-explore"><img src="https://agentmods.dev/badge/skills/pedromosquera/squadai/sdd-explore.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.00443 |
| Opus 5.5 | $0.00006 | $0.00177 |
| Sonnet 5.5 | $0.00003 | $0.00089 |
| Haiku 4.5 | $0.00002 | $0.00044 |
Grade A, and why
sdd-explore 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 15d 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 Explore Skill
Analyze an existing codebase to gather context before proposing solutions. This is the first phase of the SDD pipeline: understand before proposing.
Steps
-
Identify entry points: Find where the relevant system behavior begins.
- Main functions, HTTP handlers, CLI commands, event listeners
- Public API surfaces (exported functions, interfaces)
- Configuration loading points
-
Trace data flow: Follow data through the system.
- How does input enter the system?
- What transformations does it undergo?
- Where is data persisted or returned?
- What are the side effects?
-
Map dependencies: Understand what depends on what.
- Internal package dependencies
- External library dependencies
- Interface boundaries and their implementations
- Circular dependency risks
-
Identify hotspots: Flag areas of concern.
- Files changed frequently in git log
- Code with high complexity or low test coverage
- Undocumented magic behavior
- Areas where the feature request will require changes
-
Document constraints: Note existing commitments.
- Public API contracts that must not break
- Performance SLAs or resource limits
- Security requirements (auth, input validation)
- Compatibility requirements (old data formats, deprecated paths)
-
Summarize for the Proposer: Produce a context document.
- Overview of relevant system components
- Key data structures and their relationships
- Constraints the Proposer must respect
- Open questions that need clarification
Output Format
## Exploration Report: <topic>
### Entry Points
- <file/function>: <description of role>
### Data Flow
<brief description or diagram>
### Key Data Structures
- <type>: <description and purpose>
### Constraints
- <constraint>: <why it exists>
### Hotspots
- <area>: <risk or complexity reason>
### Open Questions
1. <question needing clarification before proposing>
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.
- 15d ago Changed a970e17d1617
- 1mo ago First seen · 71 lines · 15 tokens per session scan A e17719d5169e
sdd-explore 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 443 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.