Borrowing it
Nothing to install: this file belongs to Openly-Useful/citewire. 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/Openly-Useful/citewire/main/CLAUDE.mdgit clone --depth 1 https://github.com/Openly-Useful/citewireWrote 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/openly-useful/citewire/claude-md)<a href="https://agentmods.dev/instructions/openly-useful/citewire/claude-md"><img src="https://agentmods.dev/badge/instructions/openly-useful/citewire/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.00606 | $0.00606 |
| Opus 5 | $0.00303 | $0.00303 |
| Sonnet 5 | $0.00121 | $0.00121 |
| Haiku 4.5 | $0.00061 | $0.00061 |
Grade A, and why
citewire 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 — 54 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md
Read PROJECT_HANDOFF.md, CLAUDE_CODE_LAUNCH_PROMPT.md, and every file in
.claude/orchestration/ before acting.
CiteWire Community is MIT licensed, zero-dependency, Node 18+ ESM, provider-neutral, attribution-first, and read-only at its public boundary. Default sources and connectors are inert until an operator explicitly enables them. The classifier and editorial engine are shadow-only and cannot publish. Credential material is represented only by opaque references and must never be stored in the public registry, logs, fixtures, or continuity artifacts.
Cloud and Karaya are separate consumers with separate account and policy boundaries. Never copy their credentials, source configuration, editorial policy, private state, or account data into Community.
Current verified baseline
- Canonical repository:
Openly-Useful/citewire. - Canonical main:
e12d9b6e8efed725a085a32e935e63e35241859a. - Public PRs #2, #3, #4, #6, #7, and #8 are merged.
https://citewire.org/returns HTTPS 200 with the verified landing page.- Main passes 119 committed tests and five release-metadata checks.
- The public product foundations now include the source registry, rights policy, RSS and MCP projections, optional Studio, credential-reference and connector boundaries, calibrated classifier, and fail-closed editorial shadow engine.
- Nothing in this baseline proves a package, registry, provider, connector, production editorial rollout, or automatic publication is active.
Active gates
- Draft orchestration PR #1 may be refreshed and validated, but not merged without separate approval.
- Openly Useful PR #8 and Karaya PR #17 are current, green, clean drafts. Keep both unmerged unless their owner gates are separately satisfied.
- Cloud PR #1 is a clean draft pinned to Community commit
10aee95; it remains undeployed and account-isolated. - npm still reports
[email protected]; Community0.2.0is not published. - Karaya automation remains a separate workstream. Public cron requests return HTTP 200 every 15 minutes, but source-level fetch health, queue age, held volume, and migration state remain unverified.
- Preserve the 41 untracked owner screenshots and every unrelated dirty worktree exactly as found.
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 · 54 lines · 606 tokens per session scan A 01a5a0a8e27d
citewire CLAUDE.md is an instructions file published in the GitHub repository Openly-Useful/citewire (1 stars, last pushed 15d ago), licensed MIT. It adds 606 tokens to every session, about $0.0030 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.