More screenshots
Works with the AI Agents you already use
Hono API Safety Check
Check Hono APIs before you deploy: CORS that echoes any origin with credentials, auth secrets in code or Wrangler vars, request data in raw() or c.html(), SQL built from requests, open redirects, missing csrf() and more.
$5
Hono API Safety Check
Example session with this skill installed
Check this project with hono-api-safety-check.
- Read your context and instructions
- Compiled the hono api safety
$ python3 scripts/check_hono.py examples/risky
BLOCK src/admin.ts:7 H02 HARDCODED_AUTH_SECRET
admin.use('*', basicAuth({ username: 'admin', password: '<redacted>' }))
Why: A JWT secret, Basic auth password, Bearer token or signed-cookie secret is written in the code (jwt({ secret: '...' }), basicAuth({ password: '...' }), bearerAuth({ token: '...' }), sign(payload, '...'), setSignedCookie(..., '...'), a fallback such as c.env.JWT_SECRET || '...') or in Wrangler vars, which Cloudflare stores as plain text. Anyone with the repository can sign tokens or log in.
Safer: Read it per request from bindings (c.env.JWT_SECRET, or env(c) from hono/adapter) in a small wrapper middleware, store it with wrangler secret put or your platform's secret store (.dev.vars only for local work), fail when it is missing, and rotate the exposed value.
BLOCK src/index.ts:16 H01 CORS_REFLECTS_ANY_ORIGIN_WITH_CREDENTIALS
BLOCK src/posts.ts:9 H02 HARDCODED_AUTH_SECRET
BLOCK src/posts.ts:14 H04 SQL_BUILT_FROM_REQUEST
BLOCK src/posts.ts:15 H03 UNESCAPED_HTML_FROM_REQUEST
BLOCK wrangler.toml:8 H02 HARDCODED_AUTH_SECRET
REVIEW src/index.ts:20 H11 WEAK_ORIGIN_CHECK
REVIEW src/index.ts:23 H17 AUTH_AFTER_ROUTES
REVIEW src/index.ts:28 H15 ERROR_DETAILS_IN_RESPONSE
REVIEW src/posts.ts:10 H13 NO_SECURE_HEADERS
REVIEW src/posts.ts:18 H19 HTML_FROM_UNCHECKED_FUNCTION
REVIEW src/posts.ts:20 H16 NO_CSRF_ON_COOKIE_FORMS
REVIEW src/posts.ts:23 H18 SESSION_COOKIE_FLAGS
REVIEW src/posts.ts:24 H12 OPEN_REDIRECT
REVIEW src/posts.ts:36 H14 UPLOAD_WITHOUT_BODY_LIMIT
(Each finding also has Why and Safer lines, as in the first one.)
Verdict: BLOCK. Checked 5 files, 4 with Hono API content.
This is a static check of file text. NOT FLAGGED is not a guarantee.
Connects securely to your tools. The creator never sees your data.
About this skill
cors({ origin: (origin) => origin, credentials: true }) lets every website call your API with your users' cookies and read the answers, and c.html() with a plain template string sends ${c.req.query('q')} to the browser unescaped, because only the html tag escapes. This skill finds those and the other Hono mistakes below before you deploy, and tells you how to fix each one.
Your agent runs a scanner on your Hono code (TypeScript and JavaScript on Cloudflare Workers, Bun, Deno or Node, including jsr:@hono/hono imports) and your wrangler.toml or wrangler.json. It skips comments and test files, follows request data (params, query, headers, cookies, body and validated input) through local variables, treats the html tag, JSX, D1 .bind() and tagged SQL templates as safe, knows that c.env bindings and env(c) are not literal secrets, and counts secureHeaders(), csrf() and bodyLimit() registered anywhere in the project. It never runs your app. It returns BLOCK, REVIEW, or NOT FLAGGED, with the file, line, reason, and a safer approach. Secrets are never printed.
What it checks
BLOCK
- H01: cors() with credentials and an origin function that returns any request origin, or an Access-Control-Allow-Origin header copied from the request
- H02: JWT, Basic and Bearer auth secrets or signed-cookie secrets written in code, as a fallback value, or in Wrangler vars (public keys and settings such as token lifetimes are left alone)
- H03: request data in raw(), in c.html() with a plain template string or a same-file function that builds one, or in dangerouslySetInnerHTML
- H04: SQL for D1, pg, Prisma or Drizzle built from request data with a template literal or + (placeholder lists and values picked from fixed choices are fine)
REVIEW
- H11: CORS credentials with origin '*', origin checks with startsWith, includes, endsWith without a dot or unanchored regexes, and csrf() that allows cross-site requests
- H12: c.redirect() to a URL from the request without an origin or allow-list check (a startsWith('/') check alone still lets /\evil.com through)
- H13: apps that serve HTML without secureHeaders()
- H14: upload routes without bodyLimit()
- H15: onError returning error messages or stack traces
- H16: cookie-auth POST routes without csrf() or SameSite session cookies
- H17: auth middleware registered after the routes it should protect
- H18: session cookies without httpOnly or secure
- H19: c.html() fed by a view function called with request data that the scanner cannot see into
What's included
- The scanner (Python 3.9+, standard library only)
- A rules guide with the reason, safer approach and official source for each rule
- A risky and a safe example Workers project (Hono routes, D1, R2 and wrangler.toml), and the real report the scanner produces on the risky one
Limits It reads each file on its own and follows request data only through variables in that file: values passed into helpers in other files and chained route definitions are not followed, and secureHeaders(), csrf() and bodyLimit() count for the whole project without matching their paths. It does not check your Hono version against security advisories, Cloudflare dashboard settings, or secrets set with wrangler secret put. NOT FLAGGED is not a guarantee.
Find more skills like this on the Claude Skills Marketplace, the Codex Skills Marketplace and the Gemini Skills Marketplace, or browse Claude Skills for Security.
Static check of Hono code and Wrangler config. Request data is followed only within one file, path-scoped secureHeaders, csrf and bodyLimit are not matched to routes, and the installed Hono version is not checked. NOT FLAGGED is not a guarantee.
How to use
- 1
Connect your agent to the Agensi MCP
Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup
- 2
Sign in to Agensi
Your agent shows a sign-in link. Sign in and click Allow.
- 3
Ask for what you need
Your agent loads this skill and uses it on your task. It always asks before buying a skill.
Reviews
No reviews yet
Be one of the first to try it. Every listed skill goes through the trust checks below.
Security scanned
Checked by our 8-point scan before listing
Fresh listing
Recently published to Agensi
Money-back guarantee
Doesn't do what its page promises? You get your money back.
Trust & safety
Security scan
Security scan passed 4 days ago
Permissions
Runs one local Python script in the terminal. It reads your project's files, writes nothing, and makes no network calls. The example project includes clearly fake, inert secrets (not-a-real-... and NOTREAL-...) for the scanner to find. Nothing in it is run.