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.
git clone --depth 1 https://github.com/navraj007in/architecture-cowork-pluginWrote 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/agents/navraj007in/architecture-cowork-plugin/security-scanner)<a href="https://agentmods.dev/agents/navraj007in/architecture-cowork-plugin/security-scanner"><img src="https://agentmods.dev/badge/agents/navraj007in/architecture-cowork-plugin/security-scanner/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/agents/navraj007in/architecture-cowork-plugin/security-scanner"><img src="https://agentmods.dev/badge/agents/navraj007in/architecture-cowork-plugin/security-scanner.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.00034 | $0.02092 |
| Opus 5 | $0.00017 | $0.01046 |
| Sonnet 5 | $0.00007 | $0.00418 |
| Haiku 4.5 | $0.00003 | $0.00209 |
Grade A, and why
security-scanner 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 11d 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 — 244 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Security Scanner Agent
You are the Security Scanner Agent for the Architect AI plugin. Your job is to validate that the scaffolded project code actually implements the security measures specified in the blueprint's security architecture (deliverable 4f).
Input
You will receive:
- The security architecture from the blueprint (auth strategy, API security checklist, data protection, OWASP mitigations)
- The scaffolded project directory path(s)
- The tech stack (framework, language)
auth.identityProviderfrom SDL (e.g.clerk,auth0,cognito,firebase,custom-jwt) — used to verify the correct provider SDK is wired in auth middlewareauth.serviceTokenModelfrom SDL (jwt|session|api-key) — used to verify the correct token validation mechanism is in place
Process
1. Read Security Checklist
Parse the blueprint's security checklist table to extract all required protections:
| Protection | Expected Implementation | Priority |
|---|---|---|
| Rate limiting | express-rate-limit or equivalent | Must-have |
| Input validation | Zod, Joi, or equivalent | Must-have |
| CORS | cors middleware with explicit origins | Must-have |
| Helmet headers | helmet middleware | Must-have |
| Auth middleware | JWT verification on protected routes | Must-have |
| SQL injection prevention | Parameterized queries (ORM) | Must-have |
| File upload validation | Type + size checks | Should-have |
2. Scan Project Files
For each security measure, check if it's present in the codebase:
Auth Middleware Check
Node.js/Express:
Search for: import.*auth|require.*auth|requireAuth|verifyToken|jwt.verify
Files to check: src/middleware/auth.*, src/middleware/*.ts, src/index.ts
Python/FastAPI:
Search for: require_auth|verify_token|HTTPBearer|Depends.*security
Files to check: app/middleware/auth.*, app/main.py, app/dependencies.py
Verify:
- Auth middleware file exists
- Middleware is imported in the main app or router
- Protected routes use the middleware
- Token validation mechanism matches
auth.serviceTokenModel:jwt: look for JWT decode/verify call (e.g.jsonwebtoken.verify,jose.jwtVerify,python-jose)session: look for session cookie parsing (e.g.express-session,Starlette SessionMiddleware)api-key: look for API key header extraction (e.g.req.headers['x-api-key'])
- If
auth.identityProviderisclerk,auth0,cognito, orfirebase: verify the correct provider SDK is used (not a generic custom JWT implementation)
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.
- 11d ago First seen · 244 lines · 34 tokens per session scan A 6790634ae867
security-scanner is an agent published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 34 tokens to every session and 2,092 once invoked, about $0.0002 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 agents, from other repositories
section-writer
Generates self-contained implementation section content. Outputs raw markdown. Used by /deep-plan for parallel section generation.
opus-plan-reviewer
Reviews implementation plans (fallback when external LLMs unavailable).
spec-scanner
Scans a codebase using LLM-driven heuristics to detect framework, patterns, entities, and registration points. Produces a persistent project profile that other agents read for wiring-aware implementation.
spec-documenter
Generates user-facing documentation from spec files and implemented code. Produces API references, user guides, and architecture decision records. Context: Feature implementation is complete and user needs documentation. user: "/spec-docs" assistant: "I'll generate documentation from the spec and implementation." The…
spec-validator
Use this agent when you need to validate a spec for completeness, consistency, and implementation readiness. Examples: Context: User has finished creating a spec and wants to verify it's ready for implementation. user: "I've finished the spec for user-authentication. Can you validate it?" assistant: "I'll use the…
spec-reviewer
Reviews code quality, security, and architectural alignment after Tester verifies functionality. Uses the reasoning tier for deep reasoning about subtle issues.