Borrowing it
Nothing to install: this file belongs to fulminate-io/knowledge-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/fulminate-io/knowledge-mcp/main/.claude/skills/prefill/SKILL.mdgit clone --depth 1 https://github.com/fulminate-io/knowledge-mcpWrote 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/fulminate-io/knowledge-mcp/prefill)<a href="https://agentmods.dev/skills/fulminate-io/knowledge-mcp/prefill"><img src="https://agentmods.dev/badge/skills/fulminate-io/knowledge-mcp/prefill/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/fulminate-io/knowledge-mcp/prefill"><img src="https://agentmods.dev/badge/skills/fulminate-io/knowledge-mcp/prefill.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.00073 | $0.02404 |
| Opus 5.5 | $0.00029 | $0.00962 |
| Sonnet 5.5 | $0.00015 | $0.00481 |
| Haiku 4.5 | $0.00007 | $0.00240 |
Grade A, and why
prefill 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 1mo 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 — 173 lines — stays where its author put it; the contents beside it link to each section on GitHub.
PREFILL — the implementer's preloaded context
What a prefill is for
The prefill exists so the implementer implements instead of asking. It is everything an engineer new to this part of the codebase would need to build the ticket correctly on the first try: where the change lands, what to reuse, what it must not break, how it will be tested, and where it lands. It is a plan ROOT with no phases and no steps, carrying the goal, the tree, the reads and the citations block and no section text at all; each numbered section below is its own section node on a positioned contains edge, written alone and read alone.
The citation rule
Every file, line, symbol, count and claim in a prefill carries the command that resolved it and was opened this session at the tree the prefill names. A citation without its command is an assertion, and an assertion in a prefill is a T1 in review. Counts are tool output pasted beside the command, labeled as floors; a hand-written "all N sites" does not exist in a prefill.
The shape
The root is an INDEX, not a document. Its sections hang off it as section
nodes on contains edges carrying a zero-based position, in the order below;
the root's tree lists them in that order with each one's size, so a reader
chooses its pages rather than loading the whole plan. Changing a section is
ONE write to that section node: no other section and not the root is
re-sent, and a planner that re-writes the whole prefill to fix a sentence has
made the mistake this shape exists to prevent.
A reviewer attaches an ANNOTATION to the section it concerns, never to the
root: correct, finding with its tier, or needed change carrying the
exact replacement text in the annotation's body. The annotation's kind and
tier ride the edge that joins it to the section as well as the annotation
node, so a reader ranks a section's annotations from an edge-metadata
traverse without opening one. The section's own body is never edited by the
reviewer. A needed change is applied by exact replacement of the quoted text,
never by retyping the section.
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.
- 1mo ago Changed · +52 lines 1470de046656
- 1mo ago First seen · 121 lines · 73 tokens per session scan A 338a6f9384de
prefill is a skill published in the GitHub repository fulminate-io/knowledge-mcp (1 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 73 tokens to every session and 2,404 once invoked, about $0.0003 per session on Opus 5.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-09-07.
Other skills, from other repositories
autoreview
Structured code review through the shared OpenClaw agent-skills installation.
omh-code-review
This is an OMH code-review workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).
revdiff-plan
Review the last Codex assistant message (plan, analysis, or proposal) with inline annotations in a TUI overlay. Extracts the most recent response from Codex rollout files and opens it in revdiff for review and annotation. Activates on "revdiff-plan", "review plan with revdiff", "annotate plan", "review last response"…
explore-unknowns
Guide the user through a quadrant walk that maps the unknowns of a task — open by listing the known knowns, then work through known unknowns, unknown knowns, and unknown unknowns one stage at a time, ending with a complete four-quadrant map in the user's hands. Use when a request is ambiguous or underspecified, the…
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…
asplos-writing-style
Use when drafting or revising ASPLOS prose — engineering the first two pages that rapid review actually reads, stating the cross-layer insight as one quotable sentence, structuring per-layer mechanism sections, writing bounded claims, and fitting everything into 11 self-contained pages that include figures and…