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 skills add kensaurus/cursor-kenji --skill audit-backend-architecturegit clone --depth 1 https://github.com/kensaurus/cursor-kenjiWrote 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/kensaurus/cursor-kenji/audit-backend-architecture)<a href="https://agentmods.dev/skills/kensaurus/cursor-kenji/audit-backend-architecture"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/audit-backend-architecture/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/kensaurus/cursor-kenji/audit-backend-architecture"><img src="https://agentmods.dev/badge/skills/kensaurus/cursor-kenji/audit-backend-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00058 | $0.04463 |
| Opus 5.5 | $0.00023 | $0.01785 |
| Sonnet 5.5 | $0.00012 | $0.00893 |
| Haiku 4.5 | $0.00006 | $0.00446 |
Grade A, and why
audit-backend-architecture 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 1mo 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 — 267 lines — stays where its author put it; the contents beside it link to each section on GitHub.
audit-backend-architecture — Distributed-Systems Pattern Maturity Audit
Degree of freedom: MIXED — Fit, presence, and adopt/defer [HIGH freedom];
Phase 0 topology probes [LOW freedom — run exactly]. Never mark a
pattern Missing if its tier is N/A.
Read-only. Assess and recommend; do not change code. Per-call timeouts,
retry+jitter, idempotency keys, cancellation → audit-resilience. This
skill checks whether the patterns exist and whether they fit.
Two lenses:
- Conformance (Phase 2) — Implemented / Partial / Missing / N/A with
file:line. - Fit / decision (Phase 3) — Adopt now / Adopt when [trigger] / Defer (premature). "Don't build this yet" is a first-class finding.
Core principle — start simple, earn every pattern
Each pattern solves a specific problem and carries a specific cost. The current consensus is modular-monolith-first: >90% of systems are well served by a well-structured monolith; premature decomposition is the #1 failure mode. A pattern is "Missing" only if the measurable trigger is present — otherwise adopting it is over-engineering, flagged as loudly as a real gap.
- Fit beats presence. "No service mesh / no CQRS" is a finding only when a trigger is present.
- Decide per interaction, not per system. Sync vs event-driven is chosen per boundary-crossing call (see references/patterns.md → Communication style).
- Distributed monolith is worse than a monolith. Shared DB + coupled deploys pays the distributed tax with none of the independence.
- Reversible steps. Prefer modular monolith, façade, outbox over premature service split or event-sourcing everywhere.
How to reason — Observe → Interpret → Classify → Severity
- Observe — topology signals + the
file:line(or "searched, none found") - Interpret — is there a present pain, a named future trigger, or no trigger?
- Classify — Implemented / Partial / Missing / N/A, then Adopt now / Adopt when / Defer
- Severity — dual-write, cascade-outage, silent inconsistency = Critical; Missing with no trigger = over-engineering, not a gap
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago Changed · +1 lines · -1 tokens per session 63a470ec29b3
- 1mo ago First seen · 266 lines · 59 tokens per session scan A e7e739074c45
audit-backend-architecture is a skill published in the GitHub repository kensaurus/cursor-kenji (9 stars, last pushed 26d ago), licensed MIT. It adds 58 tokens to every session and 4,463 once invoked, about $0.0002 per session on Opus 5.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-09-03.
Other skills, from other repositories
python-dev
Python backend conventions for this project. Use when implementing or modifying API endpoints, database models/migrations, services, schemas, or backend tests.
developing-genkit-dart
Use when building AI agents in Dart, implementing Genkit flows or tools, integrating LLMs into Dart or Flutter applications, or using Genkit Dart plugins.
create-handler
Create a new API handler following the handler pattern. Use when the user asks to create an endpoint, handler, or route.
generate-api-docs
Generate API documentation from code.
api-docs
Workflow for creating comprehensive API documentation. Use when the user needs to document API endpoints.
opensearch
Workflow for OpenSearch (or Elasticsearch) usage: indexing, search, mappings, and tuning. Use when the user asks about OpenSearch/Elasticsearch.