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 agentmods add skills/eigent-ai/agent-skills/specnpx skills add eigent-ai/agent-skills --skill specgit clone --depth 1 https://github.com/eigent-ai/agent-skillsWrote 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/eigent-ai/agent-skills/spec)<a href="https://agentmods.dev/skills/eigent-ai/agent-skills/spec"><img src="https://agentmods.dev/badge/skills/eigent-ai/agent-skills/spec.svg" alt="Measured on agentmods" 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 | $0.00052 | $0.00383 |
| Opus 5 | $0.00026 | $0.00192 |
| Sonnet 5 | $0.00010 | $0.00077 |
| Haiku 4.5 | $0.00005 | $0.00038 |
Grade A, and why
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 5d 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.
What it actually says
Spec
Overview
Use this skill to turn a feature, API, refactor, or product idea into a clear specification that can feed planning and implementation. The output should reduce ambiguity before code is written.
Workflow
- Identify the problem, goal, users, constraints, and non-goals.
- Capture the current behavior or system context when relevant.
- Define user stories or use cases with acceptance criteria.
- Specify functional requirements, edge cases, error states, permissions, and data handling.
- Include API, UI, migration, observability, performance, or rollout requirements when applicable.
- List open decisions and assumptions explicitly.
- Keep the spec implementation-aware but avoid over-prescribing internal code structure unless required.
Output Pattern
Use this structure by default:
- Summary.
- Problem statement.
- Goals and non-goals.
- Users and use cases.
- Requirements.
- Acceptance criteria.
- Edge cases and risks.
- Observability, rollout, and rollback notes.
- Open questions.
Example Prompts
/spec - Build a CSV export feature for our analytics dashboard. Users need to export filtered data with custom date ranges. Support up to 100k rows./spec - Design a public webhooks API for our platform. Third-party apps need to subscribe to user events and receive payloads reliably with retry logic./spec - Refactor our authentication flow to support SSO. We need to keep existing email/password working and add Google and GitHub OAuth without breaking current sessions.
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.
- 5d ago First seen · 41 lines · 52 tokens per session scan A 522cbaaede0a
spec is a skill published in the GitHub repository eigent-ai/agent-skills (17 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 52 tokens to every session and 383 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-30.
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…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…