Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add chiz0me/express-recon/plugin install express-reconWrote 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/chiz0me/express-recon/express-recon-audit)<a href="https://agentmods.dev/skills/chiz0me/express-recon/express-recon-audit"><img src="https://agentmods.dev/badge/skills/chiz0me/express-recon/express-recon-audit/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/chiz0me/express-recon/express-recon-audit"><img src="https://agentmods.dev/badge/skills/chiz0me/express-recon/express-recon-audit.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.00118 | $0.03061 |
| Opus 5 | $0.00059 | $0.01530 |
| Sonnet 5 | $0.00024 | $0.00612 |
| Haiku 4.5 | $0.00012 | $0.00306 |
Grade A, and why
express-recon-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 — 277 lines — stays where its author put it; the contents beside it link to each section on GitHub.
HTTP route audit (express-recon)
Drives the express-recon harness to enumerate routes and flag unauthenticated
ones. The harness parses JS/TS statically (no app boot) and classifies each
route as proven (behind known auth), public (no recognised auth), or
unknown (guarded only by an opaque inline middleware).
These labels are configuration-relative. public is not proof that a route is
internet-reachable, and proven is not proof that the configured guard's
implementation is correct. Never present either label as a deployment fact.
0. Locate the tool
Use whichever resolves first:
express-reconon PATH (globally installed), elsenode ${CLAUDE_PLUGIN_ROOT}/src/cli.js(when running as an installed plugin; if${CLAUDE_PLUGIN_ROOT}/node_modulesis missing, runnpm install --omit=dev --prefix ${CLAUDE_PLUGIN_ROOT}once first), elsenode <path-to-express-recon>/src/cli.js(a local repo checkout).
If none is available, tell the user how to install it (npm i -g the
express-recon checkout) and stop.
All commands below take --src <repoDir> (one target repository root, default
cwd). Start with express-recon discover --src <repoDir> on an unfamiliar or
multi-package repository; use its stable application IDs and coverage evidence
rather than assuming there is one app.
1. Discover auth middleware (don't guess the allowlist)
The audit is only as good as the auth allowlist. Discover candidates first:
express-recon suggest-auth --src <repoDir>
This returns JSON candidates ranked with likely guards first (likelyAuth,
partial route coverage). Pick the ones that are genuinely authentication /
signature / authorization middleware — names like requireAuth,
passport.authenticate, verifyToken, *SignatureVerifier, ensureLoggedIn.
Ignore body parsers, loggers, CORS, helmet, compression.
If a guard appears inside a wrapper call such as asyncHandler(requireAuth),
add the outer callee to authWrappers only after verifying that it always
executes and preserves the wrapped middleware. Unconfigured wrappers remain
unknown; this avoids proving conditional or disabling wrappers as safe.
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 Changed · +24 lines · +10 tokens per session 9562a71d6a6d
- 10d ago First seen · 253 lines · 108 tokens per session scan A f7d9abb6bb90
express-recon-audit is a skill published in the GitHub repository chiz0me/express-recon (0 stars, last pushed yesterday), licensed MIT. It adds 118 tokens to every session and 3,061 once invoked, about $0.0006 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
mem0-oss-to-platform
Plan and then execute a migration of a project from the mem0 open-source / self-hosted SDK (the local Memory class) to the mem0 Platform / hosted / managed SDK (the MemoryClient class). Use this whenever a developer wants to move, switch, or migrate their mem0 usage off OSS/self-hosted to the hosted API — e.g.…
agui-dotnet-protobuf
Use the protobuf wire transport (instead of the default Server-Sent Events) for an AG-UI connection with the AG-UI .NET SDK — a compact binary event stream negotiated via the Accept header. USE FOR: making an AGUIChatClient prefer protobuf by wiring an AGUIEventStreamHandler with ProtobufEventStreamFormatter (then…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
fastapi-router-py
Create FastAPI routers with CRUD operations, authentication dependencies, and proper response models. Use when building REST API endpoints, creating new routes, implementing CRUD operations, or adding authenticated endpoints in FastAPI applications.
migrate-segw-to-rap
Reverse-engineer a SEGW-built OData V2 service (MPC/DPC/MPCEXT/DPCEXT) into a modern RAP V4 service — tables, CDS views (interface + projection), behavior definitions, draft entities, service definition + binding. Use when asked to "migrate this SEGW service to RAP", "convert OData V2 to V4 RAP", "modernize this…
telnyx-messaging-hosted-curl
Set up hosted SMS numbers, toll-free verification, and RCS messaging. Use when migrating numbers or enabling rich messaging features. This skill provides REST API (curl) examples.