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/ddddjaak/se-skills/code-static-reviewnpx skills add ddddjaak/se-skills --skill code-static-reviewgit clone --depth 1 https://github.com/ddddjaak/se-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/ddddjaak/se-skills/code-static-review)<a href="https://agentmods.dev/skills/ddddjaak/se-skills/code-static-review"><img src="https://agentmods.dev/badge/skills/ddddjaak/se-skills/code-static-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.1 | $0.00129 | $0.03522 |
| Opus 5 | $0.00064 | $0.01761 |
| Sonnet 5 | $0.00026 | $0.00704 |
| Haiku 4.5 | $0.00013 | $0.00352 |
Grade A, and why
code-static-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 — 258 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Code Static Review
Overview
A static code review verifies that source code conforms to the company coding standards — before it reaches peer review, integration testing, or release. Unlike a design review (which asks "is the design correct?"), a static review asks "does this code follow the rules?" The rules are prescribed by the Software Static Review Checklist: line length, indentation, brace style, naming conventions, annotation format, function structure, register definition patterns, and more.
This skill reads source files against the checklist item by item, records every violation with a traceable citation (checklist ID + file:line), and produces a compliance report. Unclear cases are flagged for SME review rather than guessed. The review is scoped explicitly to the files the user specifies — no architecture documents, no requirements, no test plans.
When to Use
- Source code is ready for peer review and needs a standards-compliance pass first
- A module is approaching code freeze and requires a formal static review checkpoint
- New team members have contributed code that must be checked against company conventions
- A legacy module is being brought under current coding standards for the first time
- Pre-commit or pre-merge compliance verification is required by the project workflow
- Register header files need verification against the register definition rules (RDC section)
When NOT to use:
- Reviewing design documents, requirements, or specifications (use
design-review) - Functional correctness testing or logic verification (this skill checks form, not behavior)
- Performance profiling, memory analysis, or dynamic analysis (out of scope)
- Reviewing documentation, build scripts, or non-code artifacts (the checklist covers C source and header files)
- When the user has not supplied specific source files to review (scope is mandatory — see Step 1)
The Process
SCOPE → CATEGORIZE → CHECK → REPORT
│ │ │ │
▼ ▼ ▼ ▼
Confirm Map files Run each Produce
which to check- checklist compliance
files list sec- item per report at
to review tions file docs/reviews/
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 · 258 lines · 129 tokens per session scan A 4227a0a35ac0
code-static-review is a skill published in the GitHub repository ddddjaak/se-skills (4 stars, last pushed 1mo ago), licensed MIT. It adds 129 tokens to every session and 3,522 once invoked, about $0.0006 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…