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 kambleakash0/agent-skills --skill spec-writergit clone --depth 1 https://github.com/kambleakash0/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/kambleakash0/agent-skills/spec-writer)<a href="https://agentmods.dev/skills/kambleakash0/agent-skills/spec-writer"><img src="https://agentmods.dev/badge/skills/kambleakash0/agent-skills/spec-writer/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/kambleakash0/agent-skills/spec-writer"><img src="https://agentmods.dev/badge/skills/kambleakash0/agent-skills/spec-writer.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.00035 | $0.01469 |
| Opus 5 | $0.00017 | $0.00734 |
| Sonnet 5 | $0.00007 | $0.00294 |
| Haiku 4.5 | $0.00003 | $0.00147 |
Grade A, and why
spec-writer 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 10d 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 — 141 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Write a Product Requirements Document
This skill turns a clarified idea into a structured PRD using conversation and repository context. It assumes that major ambiguities have already been grilled out (for example with /grill-me), but it can also perform its own lightweight clarification when needed.
When to Use
Use this skill when the user:
- Asks to "write a PRD", "product spec", "requirements doc", "feature specification", or similar.
- Wants to document a new feature, change, or system in a structured way before implementation.
- Has already clarified the idea and now needs a single, coherent document you can file as an issue, share with stakeholders, or feed into
/slice-the-spec.
If the idea is still fuzzy or underspecified, recommend using /grill-me first and then come back to this skill.
Overall Workflow
You may skip or compress steps that are clearly already complete (for example, if the user pastes a detailed problem statement or user story list).
-
Collect a rich problem description
- Ask the user for a long, detailed description of:
- The problem they want to solve
- Who it is for
- Why it matters now
- Any initial solution ideas or constraints they already have
- Encourage them to paste existing context (docs, tickets, research) instead of re‑typing everything.
- Ask the user for a long, detailed description of:
-
Explore the repo and verify assumptions
- Inspect the codebase to understand current behavior, relevant modules, data models, and existing APIs.
- Cross‑check the user’s assertions: note where the repo agrees, disagrees, or is silent, and adjust your understanding accordingly.
- Capture any repo‑grounded facts that will matter for scope, edge cases, or implementation constraints.
-
Consider alternative approaches
- Ask the user whether they have considered other solution options or design directions.
- Briefly outline 2–3 plausible approaches, with trade‑offs (complexity, time‑to‑ship, risk, UX impact).
- Confirm which approach you should treat as the primary one for this PRD.
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.
- 10d ago First seen · 141 lines · 35 tokens per session scan A 620eba2d2a09
spec-writer is a skill published in the GitHub repository kambleakash0/agent-skills (9 stars, last pushed yesterday), licensed MIT. It adds 35 tokens to every session and 1,469 once invoked, about $0.0002 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
weather
Get current weather and forecasts (no API key required).
canvas-design
Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.
dashboard-builder
Build self-contained interactive HTML dashboards with charts, filters, and tables. Generates a single browser-openable file — no server or dependencies required.
bionic-decision-engine
Unified mathematical arbitrator for all resource allocation decisions — money, time, energy, relationships. Absorbs 46 decision protocols + 24 strategy protocols into one dense engine.
gemigo-cli
Use when the user wants to publish an already-built static website or front-end app through GemiGo, such as a Vite/React/Vue static build, plain HTML/CSS/JS page, landing page, demo, docs site, or small browser app, and get a hosted public URL.
clawhub-nextclaw
Use when the user wants to search external ClawHub skills or install a ClawHub skill into a NextClaw workspace's skills directory without treating ClawHub as the NextClaw marketplace.