Borrowing it
Nothing to install: this file belongs to nawodyaishan/universal-mcp-sync. 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/nawodyaishan/universal-mcp-sync/main/.gemini/skills/agentic-sdd-plan/SKILL.mdgit clone --depth 1 https://github.com/nawodyaishan/universal-mcp-syncWrote 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/nawodyaishan/universal-mcp-sync/agentic-sdd-plan)<a href="https://agentmods.dev/skills/nawodyaishan/universal-mcp-sync/agentic-sdd-plan"><img src="https://agentmods.dev/badge/skills/nawodyaishan/universal-mcp-sync/agentic-sdd-plan/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/nawodyaishan/universal-mcp-sync/agentic-sdd-plan"><img src="https://agentmods.dev/badge/skills/nawodyaishan/universal-mcp-sync/agentic-sdd-plan.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.00022 | $0.00545 |
| Opus 5 | $0.00011 | $0.00272 |
| Sonnet 5 | $0.00004 | $0.00109 |
| Haiku 4.5 | $0.00002 | $0.00055 |
Grade A, and why
agentic-sdd-plan 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 12d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic SDD Plan
Use this skill after the spec is clear enough to design the technical approach.
Goal
Create specs/<feature>/plan.md and related planning artifacts. Do not implement code in this phase.
Required Reading
.specify/memory/constitution.mddocs/vision.mdspecs/<feature>/spec.mdspecs/<feature>/clarify.md, if present- relevant ADRs in
docs/adr/ - relevant source files and tests
- existing API contracts, schemas, migrations, and deployment config when affected
Research Rules
Use Exa advanced search when:
- a framework, SDK, or platform behavior may have changed
- security guidance is current-version sensitive
- a public API contract is involved
- the plan depends on official docs
Prefer official docs, maintained repositories, standards, and primary sources. Record only facts that affect the plan.
Plan Sections
Create or update specs/<feature>/plan.md with:
- summary
- inputs reviewed
- assumptions
- architecture approach
- affected modules
- API and contract changes
- data model changes
- dependency changes with alternatives and approval status
- security impact
- authorization boundaries
- observability impact
- testing strategy
- failure modes
- rollback and recovery
- risks and mitigations
- human architecture approval status
Create additional files when relevant:
data-model.mdcontracts/openapi.yamlcontracts/events.mdtest-plan.md- ADR draft in
docs/adr/
Architecture Rules
- Prefer existing project patterns and framework features.
- Avoid speculative abstractions.
- Justify every new dependency.
- Do not silently change auth, payments, data retention, or production operations.
- Include rollback for migrations and operationally risky changes.
- Include verification commands or observable results.
Stop Conditions
Stop and request human input when:
- dependency addition is proposed
- database migration is required
- auth, authorization, payments, secrets, or production config are touched
- rollback is not realistic
- tests or verification cannot be defined
- the plan conflicts with constitution or ADRs
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.
- 12d ago First seen · 90 lines · 22 tokens per session scan A 6160a72fe0ca
agentic-sdd-plan is a skill published in the GitHub repository nawodyaishan/universal-mcp-sync (6 stars, last pushed 1mo ago), licensed MIT. It adds 22 tokens to every session and 545 once invoked, about $0.0001 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-31.
Other skills, from other repositories
agent-manager
Run a fleet of AI coding agents as live tmux sessions with agent-manager. Use when a developer is running more than one coding agent, needs to see which one is working or blocked, wants to spawn another on an independent task, or wants to review an agent's diff without leaving the terminal.
agent-manager-reference
Query agent-manager.dev's reference API and MCP server for documentation, the coding CLIs it manages, the tools its MCP server exposes, and the current release. Use instead of scraping the website's HTML.
tui-design
Design, build, refactor, or review terminal interfaces—full-screen TUIs, interactive prompts, and command-line tools. Use for terminal-app layout and UX, CLI behavior, ncurses-style tools, dashboards, REPLs, fzf-like pickers, and libraries such as Bubble Tea, Ratatui, Textual, or Ink, including requests that name a…
subagent-driven-development
Orchestrating sub-agents through TDD phases for complex features.
systematic-debugging
4-phase debugging protocol for diagnosing and fixing failing tests.
test-driven-development
Red-green-refactor TDD implementation cycle.