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 iampawan/Manifest --skill critic-instrumentationgit clone --depth 1 https://github.com/iampawan/ManifestWrote 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/iampawan/manifest/critic-instrumentation)<a href="https://agentmods.dev/skills/iampawan/manifest/critic-instrumentation"><img src="https://agentmods.dev/badge/skills/iampawan/manifest/critic-instrumentation/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/iampawan/manifest/critic-instrumentation"><img src="https://agentmods.dev/badge/skills/iampawan/manifest/critic-instrumentation.svg" alt="Reviewed on agentmods" width="80" 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.00041 | $0.01030 |
| Opus 5 | $0.00020 | $0.00515 |
| Sonnet 5 | $0.00008 | $0.00206 |
| Haiku 4.5 | $0.00004 | $0.00103 |
Grade A, and why
critic-instrumentation 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 10d 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 — 122 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Instrumentation coverage critic
Protocol: Follow
reference/CRITIC-RULES.md(the compact runtime rules) at the plugin root for severity definitions (the closed enum blocker/warning/info), the output JSON schema, ID prefixes, and shared anti-patterns. This skill defines only WHAT to look for. Do not invent severities like "high"/"medium" — the validator rejects them. Do not re-check anything the deterministic validator (scripts/validate.mjs) already covers; add the judgment layer on top.
The single most important critic. If this doesn't pass, the post-launch report cannot run, and you can't say whether the feature landed.
What to check
1. Every behavior has a measurement plan
Each ### B<N> block must declare ONE of the following — the
plan for how this behavior will be measured post-launch:
# Option A: Client-side analytics event (preferred when project has
# Firebase Analytics, Amplitude, etc.)
- instrumentation:
source: firebase-analytics # or amplitude / segment
eventName: snake_case_name
properties: [prop_a, prop_b]
expectedRatePerDay: <integer>
# Option B: Server-side structured log event (when no client analytics)
- instrumentation:
source: server-log
logger: "audit" # logger name / channel
eventName: snake_case_name
fields: [user_id, action, ...]
expectedRatePerDay: <integer>
# Option C: Database-derived metric (for record-count behaviors)
- instrumentation:
source: database
dbQuery: "SELECT count(*) FROM payment_methods WHERE created_at > NOW() - INTERVAL '1 day'"
expectedRatePerDay: <integer>
# Option D: Sentry release adoption (for "no regression" metrics)
- instrumentation:
source: sentry-release
releaseTag: <release-id>
metric: error_rate | adoption_pct | p95_latency
target: < 0.5% # or whatever budget
# Option E: Manual reporting (lowest-quality fallback)
- instrumentation:
source: manual
rationale: "No measurement infra; PM reports weekly in Slack thread"
cadence: weekly
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.
- 10d ago First seen · 122 lines · 41 tokens per session scan A 3ca0227d2ed1
critic-instrumentation is a skill published in the GitHub repository iampawan/Manifest (5 stars, last pushed 8d ago), licensed MIT. It adds 41 tokens to every session and 1,030 once invoked, about $0.0002 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…
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…