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/thiientv/godmode/receiving-code-reviewnpx skills add thiientv/godmode --skill receiving-code-reviewgit clone --depth 1 https://github.com/thiientv/godmodeWhat 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.00067 | $0.00386 |
| Opus 5 | $0.00034 | $0.00193 |
| Sonnet 5 | $0.00013 | $0.00077 |
| Haiku 4.5 | $0.00007 | $0.00039 |
Grade A, and why
receiving-code-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 3d 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.
What it actually says
Receiving Code Review
Treat feedback as evidence to investigate, not as an attack to win or a list to obey blindly.
Classify each finding
- Defect: violates the request, contract, safety, or compatibility.
- Missing proof: behavior may be correct but the evidence is insufficient.
- Clarification: intent or ownership is unclear.
- Preference: stylistic and not worth changing unless it reduces risk.
- Out of scope: real issue for a separate owner or change.
For a defect, reproduce the failure or inspect the real code path before editing. For a disputed finding, state the invariant and the evidence that supports the decision. Do not dismiss a comment because the suite is green.
Fix loop
- Record the finding and its scope classification.
- Add a failing regression test or a direct falsifying check when practical.
- Make the smallest correction at the owning boundary.
- Run focused checks, then the relevant broader checks.
- Re-read the changed diff and reply with the exact evidence.
- Request re-review for changed contracts or previously disputed findings.
Do not bundle unrelated cleanup or change the product contract to silence a reviewer. Use finding-log.md for multiple comments.
Completion condition
Every in-scope finding is fixed, verified, or explicitly accepted with a reason; out-of-scope work is recorded for follow-up; and the re-review boundary is clear.
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.
- 3d ago First seen · 45 lines · 67 tokens per session scan A aaefd836c067
receiving-code-review is a skill published in the GitHub repository thiientv/godmode (93 stars, last pushed 8d ago), licensed MIT. It adds 67 tokens to every session and 386 once invoked, about $0.0003 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-30.
Other skills, from other repositories
establishing-project-context
Use when the user asks to establish shared project language, or project work exposes a conflicting, renamed, or deprecated domain term that needs active semantic modeling. Routine small tasks stay on the fast path.
autoprompt
Explicit-only useful-first orchestration. Invoke /autoprompt to turn a mission into one executable roadmap, build dependency-safe lanes, and verify the result with independent reviewers. Never infer invocation from ordinary requests. Never resume from leftover artifacts without an explicit resume instruction.
office-hours
YC Office Hours — two modes. Startup mode: six forcing questions that expose demand reality, status quo, desperate specificity, narrowest wedge, observation, and future-fit. Builder mode: design thinking brainstorming for side projects, hackathons, learning, and open source. Saves a design doc. Use when asked to…
memstack-business-gdpr
Use this skill when the user says 'GDPR', 'data protection', 'privacy compliance', 'DPA', 'DSAR', 'data subject request', 'cookie consent', 'privacy audit', 'CCPA', or asks 'do I need GDPR for this repo'. Scans the repository to detect what personal data is collected, classifies sensitivity, determines whether GDPR…
mathodology-whole-project
Use when running, backing up, transferring, restoring, archiving, or installing (project-level or global) the Mathodology skills-only repository and its award workflows.
map-fast
Minimal workflow for small, low-risk changes — no planning, no learning.