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 commands/naimkatiman/continuous-improvement/workspace-surface-auditgit clone --depth 1 https://github.com/naimkatiman/continuous-improvementWrote 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/commands/naimkatiman/continuous-improvement/workspace-surface-audit)<a href="https://agentmods.dev/commands/naimkatiman/continuous-improvement/workspace-surface-audit"><img src="https://agentmods.dev/badge/commands/naimkatiman/continuous-improvement/workspace-surface-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 | $0.00021 | $0.00511 |
| Opus 5 | $0.00010 | $0.00255 |
| Sonnet 5 | $0.00004 | $0.00102 |
| Haiku 4.5 | $0.00002 | $0.00051 |
Grade A, and why
workspace-surface-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 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.
How it starts
The opening of the file, as written. The whole thing — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/workspace-surface-audit
Audit the active repo, MCP servers, plugins, connectors, env surfaces, and harness setup. Returns a 5-section report with specific next moves.
Usage
/workspace-surface-audit
What It Checks
- Repo surface —
package.json, lockfiles, framework config,.mcp.json,.claude/settings*.json,AGENTS.md - Environment surface —
.env*files (key names only, no secrets) - Connected tools — installed plugins, MCP servers, LSPs, app integrations
- continuous-improvement surface — existing skills, commands, hooks, agents
Output Format
=== Workspace Surface Audit ===
## Current Surface
- [What is usable right now]
## Parity
- [Where continuous-improvement matches or exceeds benchmarks]
## Primitive-Only Gaps
- [Tools exist, but continuous-improvement lacks clean operator skills]
## Missing Integrations
- [Capabilities not available yet]
## Top 3-5 Next Moves
1. [Concrete continuous-improvement-native addition]
2. [Ordered by impact]
Rules
- Never print secrets — only provider names, capability names, file paths
- Prefer continuous-improvement over generic "install another plugin" advice
- Organize by workflows, not API brands
- Specific recommendations — concrete enough to implement without another discovery pass
Example Output
## Current Surface
- MCP: filesystem, github, playwright
- Plugins: beginner, expert (continuous-improvement)
- Env: STRIPE_API_KEY, FAL_KEY configured
- Framework: Next.js 15, React 19, TypeScript
## Parity
- Continuous improvement: covered (native)
- Testing discipline: covered (TDD workflows)
## Primitive-Only Gaps
- Stripe connected but no billing-operator skill
- GitHub MCP available but no issue-triage workflow
## Missing Integrations
- No Linear connector detected
- No Slack webhook configured
## Top 3-5 Next Moves
1. Create billing-operator skill (Stripe integration)
2. Create github-ops workflow for issue triage
3. Add Linear connector skill for project management
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 · 78 lines · 21 tokens per session scan A efbb7aa5cec0
workspace-surface-audit is a command published in the GitHub repository naimkatiman/continuous-improvement (7 stars, last pushed 10d ago), licensed MIT. It adds 21 tokens to every session and 511 once invoked, about $0.0001 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 commands, from other repositories
battlecard
Create a sales-ready competitive battlecard — positioning, feature comparison, objection handling, and win strategies.
release
Generate changelog, bump version, and create git tag.
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
analyze-and-create-issue
Analyze codebase and create GitHub/GitLab/Forgejo issues per finding.
generate-report
Generate a professional HTML report from assessment results in the conversation.
data-flow-analysis
Trace how data flows through the system from input to output.