Borrowing it
Nothing to install: this file belongs to mathpluscode/bibtools. 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/mathpluscode/bibtools/main/AGENTS.mdgit clone --depth 1 https://github.com/mathpluscode/bibtoolsWrote 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/mathpluscode/bibtools/agents-md)<a href="https://agentmods.dev/instructions/mathpluscode/bibtools/agents-md"><img src="https://agentmods.dev/badge/instructions/mathpluscode/bibtools/agents-md/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/instructions/mathpluscode/bibtools/agents-md"><img src="https://agentmods.dev/badge/instructions/mathpluscode/bibtools/agents-md.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.00706 | $0.00706 |
| Opus 5.5 | $0.00282 | $0.00282 |
| Sonnet 5.5 | $0.00141 | $0.00141 |
| Haiku 4.5 | $0.00071 | $0.00071 |
Grade A, and why
bibtools AGENTS.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 2mo 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 — 51 lines — stays where its author put it; the contents beside it link to each section on GitHub.
bibtools
A bibliography toolkit for LaTeX, built as agent skills. Explore the repo to understand the project structure before making changes.
General principles
Bias toward action. Do not spend excessive time exploring files or asking clarifying questions when the task is clear. Start implementing and iterate.
Code changes
- When fixing bugs or implementing changes, do NOT fix things that aren't actually broken. If you're unsure whether something is a real bug, ask before implementing a fix. Never apply fixes for theoretical issues that can't occur in practice given the actual workflow.
- When making changes, always check README.md and other documentation files for references that need updating. Check for hardcoded magic numbers that should use existing config values.
Code review
When asked to do a code review, only flag real actionable issues. Do NOT over-engineer fixes or apply unnecessary changes. When in doubt, propose the fix and wait for user approval before implementing.
How it works
bibtidy
In Claude Code, invoke with /bibtidy refs.bib. In Codex, ask it to use the bibtidy skill on a .bib file. The agent reads the file, dispatches parallel subagents to verify entries against Google Scholar and CrossRef (bundled crossref.py), then applies fixes sequentially with targeted edits. Every change includes the original entry commented out and one or more source URLs for verification.
Versioning
Version is tracked in three files (.claude-plugin/marketplace.json, .claude-plugin/plugin.json, pyproject.toml). Update all three, then run uv lock to sync uv.lock.
Development
The skill's tools live under skills/bibtidy/tools/ in this repo. At runtime, determine which agent platform you are (Claude Code, Codex, etc.) and resolve the installed tools directory accordingly (e.g. ~/.claude/skills/bibtidy/tools for Claude Code, ~/.codex/skills/bibtidy/tools for Codex). To test local changes:
- Run
./tests/run_bibtidy_cc_tests.sh— this syncs local tools to~/.claude/skills/bibtidy/before invoking Claude - Run
./tests/run_bibtidy_codex_tests.shfor the Codex end-to-end path - Unit tests only:
uv run pytest tests/
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.
- 2mo ago First seen · 51 lines · 706 tokens per session scan A 2795db9c08d8
bibtools AGENTS.md is an instructions file published in the GitHub repository mathpluscode/bibtools (6 stars, last pushed 6mo ago), licensed MIT. It adds 706 tokens to every session, about $0.0028 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-31.
Other instructions, from other repositories
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.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, cache eligibility and rollout and applying the notice (cutover).
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 copilot-instructions.md
Copilot instructions for microsoft/vscode, covering vs code copilot instructions, project overview, root folders, core architecture (src/ folder) and built-in extensions (extensions/ folder).
deepseek-harness AGENTS.md
AGENTS.md instructions for deepseek-ai/deepseek-harness, covering agents.md, pre-stable apis and released session data, repository layout, commands and host sandbox failures.