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 kzytateishi/spikeee-plugins-marketplace --skill specifygit clone --depth 1 https://github.com/kzytateishi/spikeee-plugins-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/kzytateishi/spikeee-plugins-marketplace/specify)<a href="https://agentmods.dev/skills/kzytateishi/spikeee-plugins-marketplace/specify"><img src="https://agentmods.dev/badge/skills/kzytateishi/spikeee-plugins-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/kzytateishi/spikeee-plugins-marketplace/specify"><img src="https://agentmods.dev/badge/skills/kzytateishi/spikeee-plugins-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.00058 | $0.00968 |
| Opus 5 | $0.00029 | $0.00484 |
| Sonnet 5 | $0.00012 | $0.00194 |
| Haiku 4.5 | $0.00006 | $0.00097 |
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 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Specify
Generate a specification for $ARGUMENTS.
Phase 1: Scenario Detection
Analyze the user's request and classify into one of 5 scenarios:
-
New Feature — keywords: "new", "add", "create", "build", "introduce" → Use refs/template-new-feature.md
-
Improvement — keywords: "improve", "optimize", "enhance", "update", "refine" → Use refs/template-improvement.md
-
Bugfix — keywords: "bug", "error", "fix", "broken", "crash", "failing" → Use refs/template-bugfix.md
-
Spike (Technical Investigation) — keywords: "investigate", "PoC", "spike", "research", "evaluate" → Use refs/template-spike.md — Also triggered by explicit prefix:
/specify spike: ... -
Chore (Technical Work) — keywords: "refactor", "migrate", "dependency", "chore", "upgrade", "infrastructure" → Use refs/template-chore.md — Also triggered by explicit prefix:
/specify chore: ...
Ambiguity handling: If the request matches keywords from multiple scenarios (e.g., "fix and improve"), STOP immediately. Output a message asking the user to choose between the top 2 matching scenarios. Do not proceed to Phase 2 until the user replies.
No match: If no keywords match any scenario, ask the user which scenario best fits their request.
Phase 2: Codebase Analysis
Before writing the specification, thoroughly analyze the existing codebase:
a. Project Environment Detection
- Language & Framework: detect from package manager and build configuration files
- Project conventions: read CLAUDE.md, AGENTS.md if present
- Architecture docs: search for docs/ or documentation/ directories
b. Related Code Investigation
- Search for files and symbols related to the feature using Grep and Glob
- If a symbolic analysis MCP is available, use it for deeper code navigation (find symbol, find references, etc.)
- Identify similar implementation patterns already in the codebase
- Check database schema/migration files if the feature involves data
- Check API routing files if the feature involves endpoints
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 105 lines · 58 tokens per session scan A 3dcf6ad07323
specify is a skill published in the GitHub repository kzytateishi/spikeee-plugins-marketplace (5 stars, last pushed 2mo ago), licensed MIT. It adds 58 tokens to every session and 968 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…