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-research-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-research-spec)<a href="https://agentmods.dev/skills/nawodyaishan/universal-mcp-sync/agentic-sdd-research-spec"><img src="https://agentmods.dev/badge/skills/nawodyaishan/universal-mcp-sync/agentic-sdd-research-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-research-spec"><img src="https://agentmods.dev/badge/skills/nawodyaishan/universal-mcp-sync/agentic-sdd-research-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.00051 | $0.00766 |
| Opus 5 | $0.00026 | $0.00383 |
| Sonnet 5 | $0.00010 | $0.00153 |
| Haiku 4.5 | $0.00005 | $0.00077 |
Grade A, and why
agentic-sdd-research-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 — 67 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agentic SDD Research Spec
Use this skill when a user asks for a spec-driven development document, a gap analysis against an SDD workflow, or an upgrade of a rough project draft into a high-quality planning artifact. The goal is a better specification, not implementation.
Operating Rules
- Treat the spec as the source of truth. Do not start coding unless the user explicitly asks for implementation.
- Read local source material first, then use Exa advanced search to validate gaps, current terminology, and official behavior.
- Prefer official documentation, primary project docs, standards, and maintained repositories over generic posts.
- Separate stable product intent from technical choices. Keep "what and why" in the spec, and "how" in the plan.
- Add explicit verification criteria. A task is not complete unless the validation command or observable result is defined.
- Flag unresolved ambiguity as an open question or clarification marker; do not silently invent risky requirements.
- Keep outputs actionable for agents: exact file paths, commands, phase gates, acceptance criteria, and stop conditions.
- Preserve the user's goal. Improve accuracy, structure, and completeness without expanding into a different product.
Workflow
-
Source Intake
- Read the user's existing draft, SDD guide, README, and repository structure.
- Identify the target artifact type: spec, plan, tasks, README, verification spec, or gap report.
- Note constraints such as "docs only", "do not develop", "zero dependency", or "no server".
-
Exa Research
- Use
web_search_advanced_exawith domain filters when possible. - Query for current official docs and recent practice discussions.
- Capture only the facts that change the document: workflow phases, verification gaps, API behavior, version-specific caveats, and security boundaries.
- Use
-
Gap Analysis
- Compare the draft against the SDD guide and research.
- Look for missing clarification phase, implementation boundaries, verification spec, success criteria, test strategy, drift prevention, dependency policy, and risk gates.
- For technical topics, verify claims against official docs before presenting them as facts.
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 · 67 lines · 51 tokens per session scan A 858bad2db2d2
agentic-sdd-research-spec is a skill published in the GitHub repository nawodyaishan/universal-mcp-sync (6 stars, last pushed 1mo ago), licensed MIT. It adds 51 tokens to every session and 766 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-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.