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 skills add Immortalqx/my_codex_skills --skill mock-reviewgit clone --depth 1 https://github.com/Immortalqx/my_codex_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/immortalqx/my_codex_skills/mock-review)<a href="https://agentmods.dev/skills/immortalqx/my_codex_skills/mock-review"><img src="https://agentmods.dev/badge/skills/immortalqx/my_codex_skills/mock-review/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/immortalqx/my_codex_skills/mock-review"><img src="https://agentmods.dev/badge/skills/immortalqx/my_codex_skills/mock-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00143 | $0.01428 |
| Opus 5 | $0.00072 | $0.00714 |
| Sonnet 5 | $0.00029 | $0.00286 |
| Haiku 4.5 | $0.00014 | $0.00143 |
Grade A, and why
mock-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 11d 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 — 176 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Mock Review
Target manuscript / venue: $ARGUMENTS
Core Boundary
This skill is for manuscript authors preparing a submission, revision, or rebuttal. The goal is to discover likely reviewer concerns early and decide how to address them.
Rules:
- Never present the output as a real official review.
- Never encourage the user to submit generated text as an actual peer review.
- Label the output as
Mock Review,Simulated Review, orSimulated Review for Author Preparation. - You may follow a venue's public review form to make the simulation realistic, but the result remains a preparation artifact for the manuscript authors.
Required Resources
Read references/output-contract.md before writing the final review.
Use scripts when available:
scripts/pdf_safety_scan.pyfor hidden text / active-content / prompt-injection-like artifact scans.scripts/extract_references.pyfor an initial references matrix from a PDF.
Working Directory Contract
Use the user's requested output location when specified. Otherwise create:
temp_codex/
venue_requirements.md
extracted_text/
scans/
metadata/
references_matrix.*
references_access_matrix.*
papers/
notes/
literature_grounding_notes.md
Default final output:
- If the user asks for
README.md, write there. - If the user specifies a path, write there.
- Otherwise write
MOCK_REVIEW.md.
Workflow
1. Identify Target and Inputs
Determine:
- venue/journal name and year/version
- main manuscript PDF
- supplementary files
- optional user-provided review template, e.g. PDF, Markdown, image/screenshot, or text
- expected final output path
If a high-impact detail cannot be inferred from filenames or local context, ask one concise question. Otherwise proceed with reasonable assumptions.
2. Research Official Review Requirements
Use current official sources for the target venue/journal:
- call for papers / author instructions
- reviewer guidelines / review criteria
- scoring rubric and field names
- page limits and supplementary rules
- rebuttal / response rules
- topic scope and desk-rejection constraints
What ships with it
4 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.
- 11d ago First seen · 176 lines · 143 tokens per session scan A 7a12c9810db0
mock-review is a skill published in the GitHub repository Immortalqx/my_codex_skills (52 stars, last pushed 1mo ago), licensed MIT. It adds 143 tokens to every session and 1,428 once invoked, about $0.0007 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
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…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
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…