Borrowing it
Nothing to install: this file belongs to stainless-code/codemap. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/stainless-code/codemap/main/.agents/skills/audit-pr-architecture/SKILL.mdgit clone --depth 1 https://github.com/stainless-code/codemapWrote 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/stainless-code/codemap/audit-pr-architecture)<a href="https://agentmods.dev/skills/stainless-code/codemap/audit-pr-architecture"><img src="https://agentmods.dev/badge/skills/stainless-code/codemap/audit-pr-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/stainless-code/codemap/audit-pr-architecture"><img src="https://agentmods.dev/badge/skills/stainless-code/codemap/audit-pr-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 6 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Prompt Injection · line 106 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 120 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 120 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 123 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 124 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
- medium Prompt Injection · line 125 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00061 | $0.03406 |
| Opus 5.5 | $0.00024 | $0.01362 |
| Sonnet 5.5 | $0.00012 | $0.00681 |
| Haiku 4.5 | $0.00006 | $0.00341 |
Grade A, and why
audit-pr-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 — 220 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Audit a PR's architecture
Mid-flight or post-merge structural review of a PR against the repo's own architecture and boundary conventions. Sister skill to pr-comment-fact-check (reviewer-comment-driven triage).
This skill exists because:
- Lightweight STOP signals (new top-level src/ folder, new shared util with 3+ consumers, folder past ~15 files without
index.ts, files moved across module boundaries) miss content-driven smells (twin wrappers, incomplete lifts, dead leftovers from a move) that show up only after the PR has been opened. - The audit recipe (codemap reindex → boundary queries → dead-code / complexity recipes → cross-check rules → write findings) is reusable but lived nowhere before this skill — every audit was rebuilding it from scratch.
When to fire
User intent (any of these phrases is enough):
- "audit this PR's architecture" / "structural review of #N"
- "check the boundaries on this branch"
- "is this PR clean / does this respect the boundaries"
- "post-merge architecture audit"
- "what did the lift miss"
- "fact-check the structural choices on this refactor"
Also fire proactively when:
- A PR moves ≥5 files between top-level
src/modules (e.g.src/cli/→src/application/, or any sibling-folder migration). - A PR introduces a new
src/<X>/subfolder. - A PR closes a structural STOP signal (so the closure is recorded with evidence).
The 6-step recipe
1. Reindex codemap and identify the diff scope
bun src/index.ts # or: codemap (from outside the repo)
git diff --name-status origin/main...HEAD
Note: the affected source modules (re-derive the live set from docs/architecture.md § Layering — today's layers include src/cli/, src/application/, src/adapters/, src/db.ts, plus runtime / config / parser modules), the PR's intent commit (the lift / extract / share), and the surrounding subtrees.
2. Derive the boundary-leak SQL kit from the repo's own architecture
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 First seen · 220 lines · 61 tokens per session scan A 2c952b0e3e18
audit-pr-architecture is a skill published in the GitHub repository stainless-code/codemap (8 stars, last pushed yesterday), licensed MIT. It adds 61 tokens to every session and 3,406 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-08-31.
Other skills, from other repositories
roam
Codebase comprehension via roam-code CLI. Use when exploring codebases, planning modifications, debugging failures, assessing PR risk, or checking architecture health. Triggers on: understanding project structure, pre-change safety checks, finding symbols/files, blast radius analysis, affected tests, health scoring…
enola
Use Enola when investigating architecture, dependencies, blast radius, cross-repository relationships, structural regressions, or what a code change did to the system.
m1nd-first
Use when investigating a repository, searching for implementation, reviewing changes, working from specs/docs, or preparing a risky code change in an environment where m1nd is available. This doctrine makes m1nd the first investigative layer before grep, glob, or manual file reads, except when the task is pure…
ctxo-domain-fold
Use BEFORE changing code under a named domain context, BEFORE finishing a branch, and when adopting or tuning the domain config, to read the context's card, fold behaviour changes back into it and discover the repository's conventions.
coograph-review
Strict read-only review of the current changes for spec compliance, convention violations, logic bugs, and architecture. Every finding cites a verbatim quote from a fresh file read. Use after implementation, before declaring done.
ctxo-review-pr
Use when reviewing a PR, a diff, or recent changes, to get a full risk assessment in one call.