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-spec/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-spec)<a href="https://agentmods.dev/skills/nawodyaishan/universal-mcp-sync/agentic-sdd-spec"><img src="https://agentmods.dev/badge/skills/nawodyaishan/universal-mcp-sync/agentic-sdd-spec/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-spec"><img src="https://agentmods.dev/badge/skills/nawodyaishan/universal-mcp-sync/agentic-sdd-spec.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.00030 | $0.00535 |
| Opus 5 | $0.00015 | $0.00267 |
| Sonnet 5 | $0.00006 | $0.00107 |
| Haiku 4.5 | $0.00003 | $0.00053 |
Grade A, and why
agentic-sdd-spec 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 11d 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 — 92 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic SDD Spec
Use this skill when creating or improving the product-facing specification for a change.
Goal
Capture what and why before deciding how. Do not design implementation in this phase.
Inputs
Read:
docs/vision.md, if present.specify/memory/constitution.md, if present- existing
specs/*/spec.md - relevant README/product docs
- user request
Use Exa only when the spec depends on current external facts, official product behavior, regulations, API behavior, or tool versions.
Spec Types
Choose one:
- feature spec
- bug fix spec
- refactor spec
- migration spec
- release/documentation spec
Feature Spec Sections
Create or update specs/<nnn-short-name>/spec.md with:
- problem statement
- goals
- non-goals
- users or actors
- user journeys
- functional requirements
- acceptance criteria
- success criteria
- edge cases
- data sensitivity and compliance notes
- API or integration expectations, without implementation design
- assumptions
- open questions
- human approval status
Clarification Rules
- Ask at most 3 clarification questions at a time.
- Ask only when the answer changes scope, security/privacy, user experience, data model, compatibility, or acceptance criteria.
- Use reasonable defaults for low-risk missing details and document them as assumptions.
- Do not proceed to planning while unresolved open questions affect implementation.
Quality Checklist
Create or update specs/<feature>/checklists/requirements.md with:
- no implementation details in spec
- goals and non-goals clear
- requirements testable and unambiguous
- acceptance criteria complete
- success criteria measurable and technology-agnostic
- edge cases identified
- data sensitivity noted
- open questions resolved or explicitly deferred
- spec ready for planning
Stop Conditions
Stop before planning if:
- user-visible behavior is ambiguous
- actors or permissions are unclear
- data sensitivity is unresolved
- success criteria are not verifiable
- the user has not approved or accepted critical clarifications
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.
- 11d ago First seen · 92 lines · 30 tokens per session scan A d3c5eadf600a
agentic-sdd-spec is a skill published in the GitHub repository nawodyaishan/universal-mcp-sync (6 stars, last pushed 1mo ago), licensed MIT. It adds 30 tokens to every session and 535 once invoked, about $0.0002 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.