audit-agent-surface
From the author
Inventory what agents can reach in a pracht app — capability exposure (HTTP, WebMCP, remote MCP), `agents` trust config, the destructive-confirmation gate, `llms.txt`, Markdown negotiation, OpenAPI — and report where the surface is wider than intended, or confirm an opt-out app ships none. Use for "audit the agent surface", "what can agents do on my site", "is my MCP endpoint safe", "did this PR widen what agents can reach".
Install
npx skills add JoviDeCroock/pracht --skill audit-agent-surface -a claude-code
Installs to .claude/skills/audit-agent-surface/ · Each command fetches the skill straight from GitHub with the open skills CLI.
Byte-identical to the scanned commit, with the repository’s licence and a SOURCE.txt.
Want your agent to suggest skills while you type? See how to use skills from your IDE.
Safety checks on SKILL.md
No warnings.
Why 83
aiqbench computes the trust score from public signals. It is not a security audit, so read a skill before you install it.
Similar skills
Closest to this one by what they do and when they are used.
- add-capabilitiesJoviDeCroock/prachtExpose an app operation as a typed pracht capability — one contract projected into direct server calls, an HTTP endpoint, a route-scoped WebMCP page tool, and a remote MCP tool — plus `defineApp({ agents })` trust config, typed clients, `<Form capability>`, and `pracht eval` scenarios. Use for "add a capability", "expose this to agents", "add an MCP tool", "add WebMCP", "serve remote MCP", "make my app agent-callable".Legal★ 105
- agent-securitynahid-sparktales/agent-dispatcherSecure an agent system as a permission surface — what authority each tool call runs under, where the confused deputy sits, which controls are enforced outside the model and which are only prompt text, and how far one bad call reaches. Use when granting an agent tools or credentials, wiring in MCP servers or subagents, reviewing an agent that acted beyond what the requester could have done, or before letting an agent touch a shared or production system. Not for wording the ingestion trust boundary in detail (prompt-injection-defense), not for scoping what an agent is for (agent-design), and it never grants an agent permission it did not already have.Security★ 59
- audit-authJoviDeCroock/prachtFind pracht routes that look protected but aren't: missing auth middleware, middleware that augments context but never gates, client-only checks, and unguarded API mutations. Use for "audit auth", "check route protection", "find unauthenticated routes", "review middleware coverage".Engineering★ 105
- seo-agenticAgriciDaniel/chatgpt-seoInspect how a website can be read and used by browsing agents. Use for agent readiness, accessibility trees, discovery files or WebMCP.Marketing★ 856
- agent-trust-boundary-auditzero-lab-ai/skillsMaps identity, authority, instruction, data, memory, and approval propagation across agents and agent-to-agent handoffs. Use when reviewing multi-agent systems, orchestrators, delegated tools, or confused-deputy exposure.Productivity★ 282
- seo-agent-readinessHainrixz/claude-seo-aiAudit how well a page can be operated by AI agents and agentic browsers — semantic interactive controls (<button>/<a href> instead of div/span click handlers), named buttons and links, labeled form controls, no javascript: hrefs, primary content outside iframes, and WebMCP detection — following Google's generative-AI guidance and the web.dev agent-friendly websites guide. Module M22 "Agent-readiness". Feeds the AI Visibility score (weight 4, all directional).Marketing★ 79
Ratings & reviews
—
no reviews
Tried this skill? Rate it to help others. Sign in
Discussion
Join the discussion. Sign in