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.
git clone --depth 1 https://github.com/gonzalezpazmonica/pm-workspaceWrote 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/commands/gonzalezpazmonica/pm-workspace/biblio-search)<a href="https://agentmods.dev/commands/gonzalezpazmonica/pm-workspace/biblio-search"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/biblio-search/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/commands/gonzalezpazmonica/pm-workspace/biblio-search"><img src="https://agentmods.dev/badge/commands/gonzalezpazmonica/pm-workspace/biblio-search.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.00033 | $0.00643 |
| Opus 5 | $0.00016 | $0.00321 |
| Sonnet 5 | $0.00007 | $0.00129 |
| Haiku 4.5 | $0.00003 | $0.00064 |
Grade A, and why
biblio-search 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 9d 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
100% identical to biblio-search — 0 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.
What it actually says
/biblio-search {proyecto} {subcommand} {args}
Subcomandos
add doi {doi}— Añade referencia consultando DOI (CrossRef)add bibtex {path}— Importa referencias desde fichero .bibadd manual {json}— Añade referencia manual (JSON)search {termino}— Busca por autor, palabra clave, añolist [--filter]— Lista todas las referencias con filtros opcionalescite {id} {formato}— Genera cita (APA, IEEE, Vancouver)export {formato}— Exporta todas a .bib u otro formato
Prerequisitos
- Verificar que
projects/{proyecto}/existe - Crear
projects/{proyecto}/bibliography/si no existe - Crear
references.jsoninicial si no existe - Validar JSON si fichero existe
Ejecución
- 🏁 Banner:
══ /biblio-search — {proyecto}/{subcommand} ══ - add doi: Consultar CrossRef con validación de formato DOI
- add bibtex: Parsear fichero .bib, extraer entradas, añadir con ID único
- add manual: Validar JSON, asignar ID (BIB-NNNN), almacenar
- search: GREP en references.json por autor/keyword/año con score relevancia
- list: Tabla con ID, autor, título, año, tipo | opciones:
--type journal|book|conference - cite: Generar formato solicitado (APA, IEEE, Vancouver) para ID específico
- export: Guardar todas las referencias en formato .bib bajo bibliography/
- Escribir agent-note:
projects/{proyecto}/agent-notes/biblio-{accion}-{fecha}.md - ✅ Banner fin con ID referencia si es add, ruta .bib si es export
Output
projects/{proyecto}/bibliography/references.json
projects/{proyecto}/bibliography/references.bib (si export)
Reglas
- Validar formato DOI:
\d{4,}/\S+antes de consultar CrossRef - Cada referencia tiene: id, doi, author, title, year, type, url, raw_bibtex
- search devuelve top 10 resultados ordenados por relevancia
- Formatos válidos para cite: APA, IEEE, Vancouver (no soportados otros)
- export SIEMPRE crea fichero nuevo con timestamp:
references-YYYYMMDD.bib
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.
- 9d ago First seen · 62 lines · 33 tokens per session scan A 9b8de80fdb3b
biblio-search is a command published in the GitHub repository gonzalezpazmonica/pm-workspace (49 stars, last pushed 6d ago), licensed MIT. It adds 33 tokens to every session and 643 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to biblio-search, differing in 0 lines, and is treated as a copy.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.