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 oaustegard/claude-skills --skill describing-productsgit clone --depth 1 https://github.com/oaustegard/claude-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/oaustegard/claude-skills/describing-products)<a href="https://agentmods.dev/skills/oaustegard/claude-skills/describing-products"><img src="https://agentmods.dev/badge/skills/oaustegard/claude-skills/describing-products/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/oaustegard/claude-skills/describing-products"><img src="https://agentmods.dev/badge/skills/oaustegard/claude-skills/describing-products.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.00165 | $0.03413 |
| Opus 5.5 | $0.00066 | $0.01365 |
| Sonnet 5.5 | $0.00033 | $0.00683 |
| Haiku 4.5 | $0.00016 | $0.00341 |
Grade A, and why
describing-products 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 2d 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 — 159 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Describing products
A product description treats the product as a large state chart the user moves through with input. The repo describes that state chart feature by feature, in plain language, from the user's side, with one skeleton for every document so that gaps and inconsistencies show up by comparison. Documents are drafted from source and tests, verified by hand against the running product, and every suspected defect lands in one triage file.
Adjacent skills: featuring inventories what a codebase does, by capability; this skill specifies how each capability behaves under every input and interruption. A _FEATURES.md is a good seed for this repo's structure, not a substitute for it.
{skill} below is this skill's directory.
| File | Use |
|---|---|
references/product-kinds.md |
Map the template onto a canvas editor, web app, CLI, chat product, or library/SDK. Read in Phase 0. |
references/README-template.md, goal-template.md, glossary-guide.md |
Skeletons for the three files that steer the build. goal-template.md carries the writing rules. |
references/document-template.md |
The eight-section skeleton every feature document follows. |
references/verification-template.md, bug-triage-template.md |
Skeletons for the checking half. |
scripts/check_links.py |
Every relative link and heading anchor resolves (GitHub slug rules). Links to documents the coverage table lists as not started are reported as planned; --strict counts them as broken. |
scripts/check_structure.py |
Coverage table matches disk; sections in order; footer present; modifier, interrupt and concern rows identical across documents; no empty cells. --exclude names extra non-feature files. |
Both scripts are stdlib Python 3, take the repo root, and exit 1 on failure.
Outputs
README.md purpose, conventions, document template, method, structure, coverage table
goal.md standing instructions for whoever drafts (you, subagents, a future session)
glossary.md the vocabulary; source of truth for every term of art
AGENTS.md "Read README.md, then goal.md. The coverage table in README.md is the work list."
CLAUDE.md "Read @AGENTS.md."
{area}/{feature}.md one document per feature, all on the same skeleton
verification/ README.md (protocol) + one checklist file per cluster of documents
bug-triage.md every suspected defect, deduplicated, with repro, cause, severity, decision needed
What ships with it
11 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.
- CHANGELOG.md 2.6 KB
- references/bug-triage-template.md 4.3 KB
- references/document-template.md 8.1 KB
- references/glossary-guide.md 3.0 KB
- references/goal-template.md 7.4 KB
- references/product-kinds.md 17 KB
- references/README-template.md 9.9 KB
- references/verification-template.md 7.0 KB
- scripts/check_links.py 6.8 KB runs code
- scripts/check_structure.py 9.5 KB runs code
- scripts/test_checks.py 4.9 KB runs code
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.
- 2d ago First seen · 159 lines · 165 tokens per session scan A a9f1afcb8a70
describing-products is a skill published in the GitHub repository oaustegard/claude-skills (153 stars, last pushed yesterday), licensed MIT. It adds 165 tokens to every session and 3,413 once invoked, about $0.0007 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-10-15.
Other skills, from other repositories
superdesign
Design or redesign frontend UI, presentations, and graphics on the Superdesign canvas with a choice of leading AI models. Use whenever the user wants to design a page, feature, flow, slide deck, or brand-new product; improve or reproduce existing UI; compare design results across top models; explore visual variants…
figma-to-code
Generate production-ready React/Next.js code from Figma designs. Instructs proper Figma MCP tool usage, component reuse strategies, and variant mapping. CRITICAL: ALWAYS use this skill when user provides a Figma link or mentions implementing/redesigning from Figma design. Never attempt manual implementation without…
smb-sales-boost
Find, preview and export growing local businesses (SMB leads) from the SMB Sales Boost database through its REST API - search by keyword, location and buying signals, preview for free, export CSV/JSON/XLSX, re-download past exports, enrich lists of website URLs, manage saved searches, keyword lists, email schedules…
Linear
Managing Linear issues, projects, and teams. Use when working with Linear tasks, creating issues, updating status, querying projects, or managing team workflows.
balzac
Balzac is an AI content platform CLI. Create workspaces, manage SEO keywords, generate article suggestions, write articles, publish content across integrations, and monitor Google Search Console performance. Supports workspaces, keywords, suggestions, briefings, articles, competitors, links, integrations, search…
balzac
AI content platform CLI. Create workspaces, manage SEO keywords, generate article suggestions, write articles, and publish to WordPress, Webflow, Wix, GoHighLevel, or webhooks.