Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add DojoGenesis/mcp --skill release-specificationgit clone --depth 1 https://github.com/DojoGenesis/mcpWrote 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/dojogenesis/mcp/release-specification)<a href="https://agentmods.dev/skills/dojogenesis/mcp/release-specification"><img src="https://agentmods.dev/badge/skills/dojogenesis/mcp/release-specification/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/dojogenesis/mcp/release-specification"><img src="https://agentmods.dev/badge/skills/dojogenesis/mcp/release-specification.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.00046 | $0.04021 |
| Opus 5.5 | $0.00018 | $0.01608 |
| Sonnet 5.5 | $0.00009 | $0.00804 |
| Haiku 4.5 | $0.00005 | $0.00402 |
Grade A, and why
release-specification 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 1mo 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 — 529 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Release Specification Skill
Version: 1.2 Author: Tres Pies Design Purpose: Write production-ready, A+ quality specifications for software releases that autonomous agents can implement without asking questions.
I. The Philosophy: Specification as Contract
A specification is not documentation — it is a contract. It is a formal agreement between the architect and the builder about what will be created, how it will work, and what success looks like. A vague specification invites confusion, rework, and failure. A rigorous specification is an act of respect for the builder's time and an investment in quality.
Specifications produced by this skill are:
- Comprehensive: Every question the builder might have is answered
- Precise: Technical details are specific, not hand-wavy
- Actionable: The path from specification to implementation is clear
- Testable: Success criteria are binary and measurable
The standard: 111/100 (A+). Good enough is not good enough.
II. When to Use This Skill
Use this skill when:
- Planning a new software version or release with multiple features or components
- Designing a complex system architecture that requires detailed documentation
- Commissioning work to an autonomous agent that needs complete context
- Coordinating parallel development tracks where specifications serve as contracts between teams
- Communicating technical vision to stakeholders, developers, or future maintainers
Do NOT use this skill for:
- Small bug fixes or minor tweaks (use a simple task description)
- Exploratory prototypes (use scouting or rapid iteration)
- Features still being actively designed (finish discovery first)
III. The Workflow
Decision Point: Full Template or Lean Format?
Before starting, determine the right spec format:
Use the Full Template (Section IV) when:
- The system is new or the architecture is unfamiliar
- The audience includes stakeholders who need context
- Multiple teams or agents will implement from this spec
- The risk profile is high (production-critical, user-facing)
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.
- 1mo ago First seen · 529 lines · 46 tokens per session scan A 12a0dd5dd09d
release-specification is a skill published in the GitHub repository DojoGenesis/mcp (0 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 4,021 once invoked, about $0.0002 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
dd-code-generation
Use pup CLI for immediate Datadog operations or generate code for integration into applications.
mma-investigator
Expert system for investigating MMA (Multi-Metric Allocator) behavior on CockroachDB clusters. Helps oncall engineers diagnose load imbalances, understand rebalancing decisions, and identify why MMA did or didn't act.
migrate-state-management
Migrate Redux or React Context to the correct state option (React Query for server state, nuqs for URL/shareable state, Zustand for global client state). Use when refactoring away from Redux/Context, moving state to the right store, or when the user asks to migrate state management.
lsp-implement
Find all concrete implementations of an interface or abstract type. Use when you need to know what types satisfy an interface, or what subtypes exist before changing a base type.
lsp-local-symbols
Fast file-scoped symbol analysis — find all usages of a symbol within the current file, list all symbols defined in the file, and get type info at a position. Use when you need local-scope analysis without a workspace-wide search.
Linux Malware Analysis
Expert ELF malware analysis — packing, toolchain ID, kill chain, persistence, C2, rootkits, cryptominers, Go/Rust/Mirai patterns, MITRE ATT&CK mapping.