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 agentmods add skills/photostructure/coding-skills/resource-reviewnpx skills add photostructure/coding-skills --skill resource-reviewgit clone --depth 1 https://github.com/photostructure/coding-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/photostructure/coding-skills/resource-review)<a href="https://agentmods.dev/skills/photostructure/coding-skills/resource-review"><img src="https://agentmods.dev/badge/skills/photostructure/coding-skills/resource-review.svg" alt="Measured on agentmods" 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 | $0.00157 | $0.03379 |
| Opus 5 | $0.00078 | $0.01690 |
| Sonnet 5 | $0.00031 | $0.00676 |
| Haiku 4.5 | $0.00016 | $0.00338 |
Grade A, and why
resource-review 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 5d 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 — 240 lines — stays where its author put it; the contents beside it link to each section on GitHub.
C/C++ Resource & Memory Review
Leaf-mode guard
If the task identifies your role as leaf-reviewer or sets
delegation-budget: 0, read and follow
references/validation-pass.md, validate only
the supplied candidates, return the verdicts to the caller, and stop before the
full workflow below.
Identify provable memory- and resource-safety defects in modern C/C++ (C++17), including Node.js native addons built with node-gyp and node-addon-api. Reason about object lifetimes and resource ownership the way an AddressSanitizer report would — then report only what you can back with concrete proof. Signal over noise.
This skill finds defects (a leak, a use-after-free, a race that actually exists). For
"is this project set up with the right hardening flags, sanitizers, CI, and conventions?"
use the project-setup skill, which assesses preventive controls, not exploitable bugs. A
missing hardening flag is not a defect; a heap-buffer-overflow is.
Scope
In scope: C and C++ translation units (.c/.cc/.cpp/.cxx/.h/.hpp), especially
Node.js native addons (Napi::ObjectWrap, AsyncWorker, ThreadSafeFunction,
finalizers), the C ABI boundary between C++ and C libraries, and the binding.gyp
defines that change runtime behavior.
Out of scope: the surrounding JavaScript/TypeScript (defer to
the web-security-review skill), and pure build-hardening/convention gaps (defer to
the project-setup skill).
Report vs. research — the prime directive
- Report on: only the file, diff, or path the user asked about.
- Research: the entire module to establish the facts — who allocates, who frees, which thread touches what, when a destructor or finalizer actually runs, and what the C library's ownership contract says.
A native defect is almost never visible in one function. Trace the allocation to its
free, the handle to its close, the pointer to the object's real lifetime, and the
napi_value to the call that created it. Never report on pattern-match alone.
What ships with it
8 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.
- 5d ago First seen · 240 lines · 157 tokens per session scan A 2c0b8c4e67ca
resource-review is a skill published in the GitHub repository photostructure/coding-skills (3 stars, last pushed yesterday), licensed MIT. It adds 157 tokens to every session and 3,379 once invoked, about $0.0008 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 skills, from other repositories
github-pr-review
Handles PR review comments and feedback resolution. Use when user wants to resolve PR comments, handle review feedback, fix review comments, address PR review, check review status, respond to reviewer, verify PR readiness, review PR comments, analyze review feedback, evaluate PR comments, assess review suggestions, or…
privacy-guard
Prevents private infrastructure details (node hostnames, internal project names, local usernames and personal emails, absolute home paths, private and VPN IP ranges) from leaking into public repositories through commits, PRs, docs or release artifacts. Use when working in a public or soon-to-be-public repo, before…
decision-records
Creates, supersedes and validates decision records (ADRs) against the convention a collection already follows, instead of imposing a published one. Use when the user wants to record a decision, write an ADR, supersede an existing decision, audit or lint a decisions folder, check that an ADR index is in sync, or asks…
github-pr-creation
Creates GitHub Pull Requests with automated validation and task tracking. Use when user wants to create PR, open pull request, submit for review, or check if ready for PR. Analyzes commits, validates task completion, generates Conventional Commits title and description, suggests labels. NOTE - for merging existing…
github-pr-merge
Merges GitHub Pull Requests after validating pre-merge checklist. Use when user wants to merge PR, close PR, finalize PR, complete merge, approve and merge, or execute merge. Runs pre-merge validation (tests, lint, CI, comments), confirms with user, merges with proper format, handles post-merge cleanup.
git-commit
Creates git commits following Conventional Commits format with type/scope/subject. Use when user wants to commit changes, create commit, save work, or stage and commit. Enforces project-specific conventions from CLAUDE.md.