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 Kin9Zeus/senior-engineer-skills --skill project-auditgit clone --depth 1 https://github.com/Kin9Zeus/senior-engineer-skillsWrote 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/kin9zeus/senior-engineer-skills/project-audit)<a href="https://agentmods.dev/skills/kin9zeus/senior-engineer-skills/project-audit"><img src="https://agentmods.dev/badge/skills/kin9zeus/senior-engineer-skills/project-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/kin9zeus/senior-engineer-skills/project-audit"><img src="https://agentmods.dev/badge/skills/kin9zeus/senior-engineer-skills/project-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.00172 | $0.02169 |
| Opus 5.5 | $0.00069 | $0.00868 |
| Sonnet 5.5 | $0.00034 | $0.00434 |
| Haiku 4.5 | $0.00017 | $0.00217 |
Grade A, and why
project-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 2d 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 — 169 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Audit
A real audit is evidence-driven. Every finding points at a line, a route, a table or a config key, and every finding carries a way to prove the fix. Opinions without locations are not findings.
Phase 0 — Scope and consent (2 minutes, never skipped)
Establish before reading code:
- What is in scope? Repository only, or also the live site, infrastructure and third-party accounts?
- What is the audit for? Pre-launch gate, investor due diligence, an inherited codebase, a security concern, or a general health check. This changes what gets weighted.
- What may be run? Read-only analysis is always safe. Ask before installing dependencies, running tests, starting services, or touching anything that reaches production.
- Is there a live URL? If yes, the
web-presence-audit,accessibility-auditandprivacy-compliancepasses become live checks rather than code inference.
Never scan, probe or send traffic to infrastructure the user has not confirmed they own or are authorised to test.
State the scope in one line and begin.
Phase 1 — Ground truth
Run the discovery protocol from senior-engineer/references/discovery-protocol.md.
scripts/recon.sh (or recon.ps1 on Windows) automates the first pass and
prints a structured summary — run it if the environment allows, and fall back to
the manual commands if not. It is read-only.
Do not proceed to findings until the Ground Truth block is filled in. An audit built on a misread stack is worse than no audit.
Phase 2 — The fifteen domain passes
Load the specialised skill for each domain rather than working from memory.
| # | Domain | Skill to load | Weight |
|---|---|---|---|
| 1 | Security | security-hardening |
15 |
| 2 | Data and persistence | database-engineering |
12 |
| 3 | Correctness and testing | testing-strategy |
11 |
| 4 | Architecture | this skill, references/architecture-review.md |
10 |
| 5 | API design | api-contracts |
7 |
| 6 | DevOps and delivery | devops-platform |
8 |
| 7 | Observability | observability-slo |
7 |
| 8 | Performance | performance-engineering |
6 |
| 9 | Accessibility | accessibility-audit |
6 |
| 10 | Web presence and SEO | web-presence-audit |
5 |
| 11 | Privacy and compliance | privacy-compliance |
6 |
| 12 | Documentation | engineering-standards |
4 |
| 13 | Dependencies and supply chain | security-hardening |
5 |
| 14 | Developer experience | engineering-standards |
4 |
| 15 | Cost and scalability | devops-platform |
4 |
What ships with it
6 files 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.
- 2d ago Changed · +15 lines e6ed3f8865bf
- 1mo ago First seen · 154 lines · 172 tokens per session scan A ede3d8b1061d
project-audit is a skill published in the GitHub repository Kin9Zeus/senior-engineer-skills (3 stars, last pushed 2d ago), licensed MIT. It adds 172 tokens to every session and 2,169 once invoked, about $0.0007 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-08-31.
Other skills, from other repositories
gotchas
Catches silent bugs that look right in a diff, compile clean, and pass happy-path tests: 200 OK HTML stand-ins, swallowed exceptions, state written before the async point of no return, module singletons shared across requests, Web APIs that fail without throwing, fresh-clone gaps, and tests that pass for the wrong…
audit
Project health audit and health check — architecture, performance, tests, dependencies, code quality. Use when assessing overall project health, before releases, or after refactors.
code-review-web
Review web application code for bugs, security issues, performance problems, and stack-specific anti-patterns. Use this skill whenever the user wants to review code, debug a production issue, investigate a build failure, audit security, or check a PR before merging. Triggers on code review, review my code, debug…
best-practices
Apply modern web development best practices for security, compatibility, and code quality. Use when asked to "apply best practices", "security audit", "modernize code", "code quality review", or "check for vulnerabilities".
polish-code
Stage, format, lint, test, review, smoke test, and re-run itself until stable. Use when the user asks to "polish code", "refine code", "iterate on code quality", "review loop", "clean up, test, and review loop", or "run the polish loop".
simplify-code
Run a multi-agent review of changed files for scope, reuse, quality, efficiency, clarity, and altitude issues followed by fixes. Use when the user asks to "simplify code", "review changed code", "check for code reuse", "review code quality", "review efficiency", "simplify changes", "clean up code", "refactor changes"…