Borrowing it
Nothing to install: this file belongs to lonexreb/cite-guard. 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/lonexreb/cite-guard/main/CLAUDE.mdgit clone --depth 1 https://github.com/lonexreb/cite-guardWrote 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/instructions/lonexreb/cite-guard/claude-md)<a href="https://agentmods.dev/instructions/lonexreb/cite-guard/claude-md"><img src="https://agentmods.dev/badge/instructions/lonexreb/cite-guard/claude-md.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.1 | $0.01260 | $0.01260 |
| Opus 5 | $0.00630 | $0.00630 |
| Sonnet 5 | $0.00252 | $0.00252 |
| Haiku 4.5 | $0.00126 | $0.00126 |
Grade A, and why
cite-guard CLAUDE.md 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 7d 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 — 108 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md — CiteGuard
Guidance for Claude Code when working in this repository.
What this project is
CiteGuard is an open, OpenAlex-native citation-integrity layer for the open-science
community. It flags references that are retracted, corrected, or subject to an
expression of concern — the nuance OpenAlex's single is_retracted boolean cannot
express — and surfaces this to librarians, research-integrity officers, systematic
reviewers, and authors.
It ships as two surfaces over one core:
- An evals-backed MCP server — the primary deliverable. Tools:
check_references,get_editorial_status,watch_institution. - A reference-list checker — paste a DOI / upload a
.bib→ per-reference status.
The differentiator vs. prior art (RetractoBot, scite, Feet of Clay) is that this is free, fully open, OpenAlex-native, and evals-backed. RetractoBot could not build this openly because no open citation database existed at the time; OpenAlex now fills that gap.
Non-negotiable design constraints
- Free-tier-aware by default. OpenAlex API keys are mandatory (since Feb 13, 2026).
Free tier ≈ $1/day.
/works?search=costs 10× a single-record lookup. Architect around cheap ID-based lookups, not bulk search. Use the free monthly snapshot subset for anything bulk; use the live API only for incremental/targeted checks. - Conservative labeling. A false "retracted" flag harms real authors — this is the exact bug OpenAlex shipped. Never over-claim. Distinguish retraction vs. correction vs. expression of concern vs. hijacked-journal. When status is ambiguous, say so.
- Evals are a first-class deliverable, not an afterthought. Every core capability needs a gold-set test with reported precision/recall. The eval harness IS the moat.
- CC0 / open ethos. Attribute Retraction Watch (via Crossref) and OpenAlex. Keep the project reproducible and well-documented (README, architecture docs, Zenodo DOI).
Data sources
- OpenAlex API — works, authors, institutions, citation graph. Requires API key
(env
OPENALEX_API_KEY), plus a polite-poolmailto. - Retraction Watch dataset — now open via Crossref. Ingest the dump; it carries the
update-naturenuance (retraction / correction / expression of concern) that we normalize into our own editorial-status model. - Crossref REST API — DOI normalization and cross-checking.
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.
- 7d ago First seen · 108 lines · 1,260 tokens per session scan A 7e46f9a07712
cite-guard CLAUDE.md is an instructions file published in the GitHub repository lonexreb/cite-guard (0 stars, last pushed 1mo ago), licensed MIT. It adds 1,260 tokens to every session, about $0.0063 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 instructions, from other repositories
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.