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 a554b554/Reactant --skill citegit clone --depth 1 https://github.com/a554b554/ReactantWrote 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/a554b554/reactant/cite)<a href="https://agentmods.dev/skills/a554b554/reactant/cite"><img src="https://agentmods.dev/badge/skills/a554b554/reactant/cite/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/a554b554/reactant/cite"><img src="https://agentmods.dev/badge/skills/a554b554/reactant/cite.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.00037 | $0.00691 |
| Opus 5.5 | $0.00015 | $0.00276 |
| Sonnet 5.5 | $0.00007 | $0.00138 |
| Haiku 4.5 | $0.00004 | $0.00069 |
Grade A, and why
cite 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 — 72 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cite
Activation Boundary
This is a tag-only worker skill. Use it only after execute or execute-one
selects an exact <@cite...> annotation in a target document and hands off its
context. Never activate it from ordinary chat, semantic similarity, or any
skill other than those two routers. Without that handoff, do not search or
change files; direct the user to add the tag and run a router.
Find a reference that supports the claim next to the tag, insert a citation, then consume the tag.
Tag
<@cite>
<@cite: source hint or search instruction>
Examples: <@cite: search arxiv>, <@cite: ``refs.bib``>,
<@cite: the original transformer paper>.
Input
- File path — the document being processed.
- Surrounding block — the maximal run of non-blank lines containing the tag; blank lines bound it. The claim to support is the statement the tag is attached to.
- Prompt (optional) — where or how to find the reference: a bibliography file, an arXiv or web search, or a description of the intended source.
Workflow
- Read the surrounding block and identify the claim that needs support.
- Determine the citation source: a referenced
.bib/.mdfile, an arXiv or web search using whatever search capability the host provides, or a specific work named in the prompt. Prefer peer-reviewed or well-cited sources when searching. - Determine the citation format from the document itself: LaTeX uses
\cite{key}; Markdown typically uses[number]or[@key]. Match the style already used in the document. - Insert the citation at the tag's position and remove the tag.
- In a LaTeX project, when citing a work not already in the bibliography, add
a BibTeX entry to the referenced or main
.bibfile. Do not duplicate an existing entry.
Context References
Double-backtick references in the prompt usually name the citation source
(for example <@cite: ``refs.bib``>). Resolve paths relative to the
document's directory unless absolute. Remove the delimiters from the output.
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 · +33 lines · +22 tokens per session 5ada9fd28d99
- 1mo ago First seen · 39 lines · 15 tokens per session scan A b783ee7e27b8
cite is a skill published in the GitHub repository a554b554/Reactant (54 stars, last pushed 1mo ago), licensed MIT. It adds 37 tokens to every session and 691 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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
Optimize the meaningful UI available immediately from a Next.js route on an initial load (hard navigation) or named client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route and entry point at a time; the shipped test then guards…