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 akka/ai-marketplace --skill specifygit clone --depth 1 https://github.com/akka/ai-marketplaceWrote 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/akka/ai-marketplace/specify)<a href="https://agentmods.dev/skills/akka/ai-marketplace/specify"><img src="https://agentmods.dev/badge/skills/akka/ai-marketplace/specify/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/akka/ai-marketplace/specify"><img src="https://agentmods.dev/badge/skills/akka/ai-marketplace/specify.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.00016 | $0.04289 |
| Opus 5 | $0.00008 | $0.02145 |
| Sonnet 5 | $0.00003 | $0.00858 |
| Haiku 4.5 | $0.00002 | $0.00429 |
Grade A, and why
specify 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 9d 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 — 301 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
You MUST consider the user input before proceeding (if not empty).
Outline
The text the user typed after /akka:specify in the triggering message is the feature description. Assume you always have it available in this conversation even if the user's request appears literally below. Do not ask the user to repeat it unless they provided an empty command.
Given that feature description, do this:
-
Prerequisite check: Before doing anything else, verify the environment is ready:
- Call
akka_sdd_list_specs— if this MCP tool is not available, the Akka MCP server is not configured. Stop and tell the user: "The Akka MCP server is not running. Run/akka:setupfirst to configure your project, or runakka specify init .from the terminal." - Check if the current directory has a
pom.xmlor.akka/directory. If neither exists, warn: "This doesn't look like an Akka project directory. Run/akka:setupto scaffold a new project, orcdinto an existing one." - If both checks pass, proceed.
- Call
-
Generate a concise short name (2-4 words) for the branch:
- Analyze the feature description and extract the most meaningful keywords
- Create a 2-4 word short name that captures the essence of the feature
- Use action-noun format when possible (e.g., "add-user-auth", "fix-payment-bug")
- Preserve technical terms and acronyms (OAuth2, API, JWT, etc.)
- Keep it concise but descriptive enough to understand the feature at a glance
- Examples:
- "I want to add user authentication" → "user-auth"
- "Implement OAuth2 integration for the API" → "oauth2-api-integration"
- "Create a dashboard for analytics" → "analytics-dashboard"
- "Fix payment processing timeout bug" → "fix-payment-timeout"
-
Check for existing branches before creating new one:
a. First, fetch all remote branches to ensure we have the latest information.
b. Find the highest feature number across all sources for the short-name:
- Remote branches:
git ls-remote --heads origin | grep -E 'refs/heads/[0-9]+-<short-name>$' - Local branches:
git branch | grep -E '^[* ]*[0-9]+-<short-name>$' - Specs directories: Check for directories matching
specs/[0-9]+-<short-name>
- Remote branches:
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.
- 9d ago First seen · 301 lines · 16 tokens per session scan A 39d080309fab
specify is a skill published in the GitHub repository akka/ai-marketplace (6 stars, last pushed yesterday), licensed Apache-2.0. It adds 16 tokens to every session and 4,289 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
gsd-plan-review-convergence
Cross-AI plan convergence - replan until review concerns are resolved.
gsd-ns-manage
Route to the appropriate management skill based on the user's intent. gsd-config (settings + advanced + integrations + profile) and gsd-workspace (new + list + remove) are post-#2790 consolidated entries.
gsd-audit-milestone
Audit milestone completion against original intent before archiving.
gsd-validate-phase
Retroactively audit and fill Nyquist validation gaps for a completed phase.
spec-kitty-charter-doctrine
Run charter interview, generation, context, and sync workflows for project governance in Spec Kitty 3.x. Access doctrine artifacts programmatically via DoctrineService. Resolve agent profiles. Load action-scoped governance context iteratively, not all at once. Triggers: "interview for charter", "generate charter"…
spec-kitty-spdd-reasons
Drive REASONS Canvas authoring and review for Spec Kitty missions that opted in to Structured-Prompt-Driven Development (SPDD) via charter selection. Triggers: "use SPDD", "use REASONS", "generate a REASONS canvas", "apply structured prompt driven development", "make this mission SPDD". Does NOT handle: enforcing SPDD…