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/junmystery/agent-guidance-python/workspace-surface-auditnpx skills add JunMystery/Agent-Guidance-Python --skill workspace-surface-auditgit clone --depth 1 https://github.com/JunMystery/Agent-Guidance-PythonWrote 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/junmystery/agent-guidance-python/workspace-surface-audit)<a href="https://agentmods.dev/skills/junmystery/agent-guidance-python/workspace-surface-audit"><img src="https://agentmods.dev/badge/skills/junmystery/agent-guidance-python/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.1 | $0.00063 | $0.01093 |
| Opus 5 | $0.00032 | $0.00547 |
| Sonnet 5 | $0.00013 | $0.00219 |
| Haiku 4.5 | $0.00006 | $0.00109 |
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 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.
This is a copy
100% identical to workspace-surface-audit — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 126 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workspace Surface Audit
Read-only audit skill for answering the question "what can this workspace and machine actually do right now, and what should we add or enable next?"
This is the ECC-native answer to setup-audit plugins. It does not modify files unless the user explicitly asks for follow-up implementation.
When to Use
- User says "set up Claude Code", "recommend automations", "what plugins or MCPs should I use?", or "what am I missing?"
- Auditing a machine or repo before installing more skills, hooks, or connectors
- Comparing official marketplace plugins against ECC-native coverage
- Reviewing
.env,.mcp.json, plugin settings, or connected-app surfaces to find missing workflow layers - Deciding whether a capability should be a skill, hook, agent, MCP, or external connector
Non-Negotiable Rules
- Never print secret values. Surface only provider names, capability names, file paths, and whether a key or config exists.
- Prefer ECC-native workflows over generic "install another plugin" advice when ECC can reasonably own the surface.
- Treat external plugins as benchmarks and inspiration, not authoritative product boundaries.
- Separate three things clearly:
- already available now
- available but not wrapped well in ECC
- not available and would require a new integration
Audit Inputs
Inspect only the files and settings needed to answer the question well:
- Repo surface
package.json, lockfiles, language markers, framework config,README.md.mcp.json,.lsp.json,.claude/settings*.json,.codex/*AGENTS.md,CLAUDE.md, install manifests, hook configs
- Environment surface
.env*files in the active repo and obvious adjacent ECC workspaces- Surface only key names such as
STRIPE_API_KEY,TWILIO_AUTH_TOKEN,FAL_KEY
- Connected tool surface
- Installed plugins, enabled connectors, MCP servers, LSPs, and app integrations
- ECC surface
- Existing skills, commands, hooks, agents, and install modules that already cover the need
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 · 126 lines · 63 tokens per session scan A dddd3e1a1716
workspace-surface-audit is a skill published in the GitHub repository JunMystery/Agent-Guidance-Python (2 stars, last pushed 1mo ago), licensed MIT. It adds 63 tokens to every session and 1,093 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to workspace-surface-audit, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
frontmcp-setup
Use when starting, scaffolding, or organizing a FrontMCP project. Covers creating a new project (CLI scaffold or manual) for Node, Vercel, and other targets; standalone versus Nx-monorepo layout, naming conventions, generators, and dependency rules; composing multiple @App classes, ESM packages, and remote MCP servers…
apitap
ApiTap gives AI agents cheap access to web data through three layers.
you-finance
Route finance questions to an existing local script, a new You.com Finance Research API call, or an MCP payment-aware fallback.
zia-look-up-rule-targets
Look up the shared 'who/where/when/what-device' fields that every ZIA rule resource scopes by — users, groups, departments, locations, locationgroups, urlcategories, devices, devicegroups, workloadgroups, labels, and timewindows — and return the IDs (or canonical strings) the rule API expects. Use this skill from…
powerpoint-mcp
PowerPoint MCP Server skill for Windows presentation automation via a live PowerPoint desktop instance (COM/PIA). Use when an assistant needs rich MCP tools to create, open, build, format, and export PowerPoint (.pptx/.pptm) presentations — slides, shapes, text boxes, tables, native charts, images, audio, video…