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/srstomp/pokayokay/feature-auditnpx skills add srstomp/pokayokay --skill feature-auditgit clone --depth 1 https://github.com/srstomp/pokayokayWrote 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/srstomp/pokayokay/feature-audit)<a href="https://agentmods.dev/skills/srstomp/pokayokay/feature-audit"><img src="https://agentmods.dev/badge/skills/srstomp/pokayokay/feature-audit.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.1 | $0.00047 | $0.00665 |
| Opus 5 | $0.00023 | $0.00332 |
| Sonnet 5 | $0.00009 | $0.00133 |
| Haiku 4.5 | $0.00005 | $0.00067 |
Grade A, and why
feature-audit 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 6d 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 — 59 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Feature Audit
Ensures features are not just implemented but actually user-accessible. Bridges the gap between "code complete" and "user can use it."
When NOT to Use
- Analyzing agent/session patterns — Use
session-reviewfor retrospectives on how work went - Security review — Use
security-auditfor vulnerability scanning; this skill checks feature completeness, not security - Creating the plan — Use
planningto break down PRDs into tasks; this skill audits after implementation
Completeness Levels
| Level | Name | Meaning |
|---|---|---|
| 0 | Not Started | No implementation evidence |
| 1 | Backend Only | Service/API exists, no frontend |
| 2 | Frontend Exists | UI components exist, not accessible |
| 3 | Routable | Has route/screen, not in navigation |
| 4 | Accessible | In navigation, users can reach it |
| 5 | Complete | Accessible + documented + tested |
Quick Start Checklist
- Discover project framework and structure
- Load feature/task context from ohno (
mcp__ohno__get_epics,mcp__ohno__get_tasks) ornpx @stevestomp/ohno-cli tasks - For each feature: check backend, frontend, route, navigation
- Assign completeness level (0-5)
- Generate report and remediation tasks
Key Principles
- Always verify in codebase — don't trust task status alone
- Check full accessibility chain: backend → frontend → route → navigation → docs
- Generate specific remediation tasks (not generic "add frontend")
- Priority follows feature priority (P0 gap = P0 remediation)
References
| Reference | Description |
|---|---|
| framework-patterns.md | Scanning patterns for each framework |
| completeness-criteria.md | Detailed level definitions and checklists |
| gap-analysis.md | Analysis methodology |
| remediation-templates.md | Task templates for common gaps |
| scanning-process.md | Backend, frontend, API, navigation scans |
| anti-patterns.md | Audit and remediation anti-patterns |
What ships with it
6 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.
- 6d ago First seen · 59 lines · 47 tokens per session scan A ff05dd283932
feature-audit is a skill published in the GitHub repository srstomp/pokayokay (9 stars, last pushed 2mo ago), licensed MIT. It adds 47 tokens to every session and 665 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
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…
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…
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…