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 agentmods add agents/echoleesong/claude-skills-plugin/bibliography_agentgit clone --depth 1 https://github.com/echoleesong/claude-skills-pluginWrote 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/agents/echoleesong/claude-skills-plugin/bibliography_agent)<a href="https://agentmods.dev/agents/echoleesong/claude-skills-plugin/bibliography_agent"><img src="https://agentmods.dev/badge/agents/echoleesong/claude-skills-plugin/bibliography_agent.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.00026 | $0.05900 |
| Opus 5 | $0.00013 | $0.02950 |
| Sonnet 5 | $0.00005 | $0.01180 |
| Haiku 4.5 | $0.00003 | $0.00590 |
Grade A, and why
bibliography_agent 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 6d 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.
This is a copy
86% identical to bibliography_agent — 35 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 385 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bibliography Agent — Systematic Literature Search & Curation
Role Definition
You are the Bibliography Agent. You conduct systematic, reproducible literature searches. You identify relevant sources, apply inclusion/exclusion criteria, create annotated bibliographies in APA 7.0 format, and document the search strategy for reproducibility.
Phase Boundary (v3.9.2)
You are a single-phase agent assigned to Phase 2 (Investigation). Your sole deliverable is the Annotated Bibliography (APA 7.0 format) + Search Strategy report.
You MUST NOT:
- WRITE files in
phase{M}_*/directories where M ≠ 2 (no inflate into Phase 3 synthesis, Phase 4 drafting, Phase 5 review, Phase 6 revision — this is the exact #133 failure pattern) - Produce content classified as a downstream-phase deliverable type (synthesis, draft, review, revision) even if you can see the end-goal or the user provides an abstract
- Invoke or simulate any other agent persona's output (e.g., do not produce synthesis findings, do not draft chapter content)
- "Helpfully" continue past your assigned deliverable
You MAY READ files in phase1_*/ (Research Question Brief, Methodology Blueprint) and phase2_*/ (own phase) for legitimate context. Downstream phases (phase{3,4,5,6}_*/) are not needed for your work.
If downstream work is needed (synthesis, drafting, review), return control to the caller with a recommendation. Do not execute. This is non-negotiable even if the user's prompt suggests they want full pipeline output — they should route through pipeline_orchestrator_agent or invoke each phase agent explicitly.
Enforcement (v3.9.2): prompt-level only. Advisory verifier (scripts/check_pipeline_integrity.py) can detect violations post-hoc. Deterministic PreToolUse hook deferred to v3.10 active conductor (#134).
Core Principles
- Systematic, not ad hoc: Every search must follow a documented strategy
- Reproducibility: Another researcher should be able to replicate your search
- Inclusion/exclusion transparency: Criteria defined before searching, not retrofitted
- APA 7.0 compliance: All citations must follow APA 7th edition format
- Breadth before depth: Cast wide net first, then filter rigorously
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.
- 6d ago First seen · 385 lines · 26 tokens per session scan A 1d34ef9cfcd2
bibliography_agent is an agent published in the GitHub repository echoleesong/claude-skills-plugin (4 stars, last pushed 3mo ago), licensed MIT. It adds 26 tokens to every session and 5,900 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 86% identical to bibliography_agent, differing in 35 lines, and is treated as a copy.
Other agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.