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/deonmenezes/mantishack/code-review-contextnpx skills add deonmenezes/mantishack --skill code-review-contextgit clone --depth 1 https://github.com/deonmenezes/mantishackWrote 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/deonmenezes/mantishack/code-review-context)<a href="https://agentmods.dev/skills/deonmenezes/mantishack/code-review-context"><img src="https://agentmods.dev/badge/skills/deonmenezes/mantishack/code-review-context.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.00007 | $0.00142 |
| Opus 5 | $0.00003 | $0.00071 |
| Sonnet 5 | $0.00001 | $0.00028 |
| Haiku 4.5 | $0.00001 | $0.00014 |
Grade A, and why
code-review-context 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 4d 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.
This is a copy
100% identical to code-review-context — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Codex maintains a context (history of messages) that is sent to the model in inference requests.
- No history rewrite - the context must be built up incrementally.
- Avoid frequent changes to context that cause cache misses.
- No unbounded items - everything injected in the model context must have a bounded size and a hard cap.
- No items larger than 10K tokens.
- Highlight new individual items that can cross >1k tokens as P0. These need an additional manual review.
- All injected fragments must be defined as structs in
core/contextand implement ContextualUserFragment trait
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.
- 4d ago First seen · 13 lines · 7 tokens per session scan A 0af80b6388cc
code-review-context is a skill published in the GitHub repository deonmenezes/mantishack (493 stars, last pushed 23d ago), licensed Apache-2.0. It adds 7 tokens to every session and 142 once invoked, about $0.0000 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to code-review-context, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
C31-compound
Capture a recently solved problem as structured documentation so future occurrences take minutes instead of research cycles.
C31-context-engineering
The core pain point of the C31 system: a 200K context window, but with poor information organization = effective capacity of only 30K.
C31-compound-refresh
Headless health check for the C31 knowledge base. Runs automatically or on-demand to keep memory/ and skills/ fresh, and evaluates whether any skill needs evolution.
hive.context-preservation
Proactively extract critical values from tool results into working notes before automatic context pruning destroys them.
exploiting-format-string-vulnerabilities
Methodology for exploiting format string bugs where attacker-controlled data reaches the format argument of printf-family functions, enabling stack/memory disclosure (info leaks for ASLR/PIE/canary defeat) and arbitrary write primitives (%n) to hijack control flow via GOT/.finiarray overwrites.
exploiting-linux-kernel-vulnerabilities
Methodology for discovering and exploiting Linux kernel memory-corruption vulnerabilities (UAF, OOB read/write, race/TOCTOU, type confusion) during authorized engagements, covering reachability analysis, building stable read/write primitives from a single bug, defeating KASLR/SMEP/SMAP/KPTI, slab/buddy heap grooming…