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 skills add flonat/flonat-research --skill bib-parsegit clone --depth 1 https://github.com/flonat/flonat-researchWrote 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/skills/flonat/flonat-research/bib-parse)<a href="https://agentmods.dev/skills/flonat/flonat-research/bib-parse"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/bib-parse/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/skills/flonat/flonat-research/bib-parse"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/bib-parse.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 74 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Rogue Agent · line 211 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00054 | $0.03743 |
| Opus 5.5 | $0.00022 | $0.01497 |
| Sonnet 5.5 | $0.00011 | $0.00749 |
| Haiku 4.5 | $0.00005 | $0.00374 |
Grade A, and why
bib-parse 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 1mo 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 — 295 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bibliography Parser — PDF to .bib
LIBRARY-FIRST RULE: ALWAYS check Paperpile membership by DOI (paperpile lookup-by-doi) for each parsed reference BEFORE generating new BibTeX entries. Topic/title search-library is a lossy discovery aid, NOT a membership test — never tag a reference NEW off a title-search miss. Reuse existing library entries instead of constructing from scratch. Enforced in Phase 2.3 per shared/reference-resolution.md § Membership Check.
Goal: given a PDF file, extract all cited references and produce a clean, validated .bib file.
When to Use
- You have a PDF (paper, report, thesis) and need a
.bibfile for its references - Importing references from a paper that doesn't have a companion
.bibfile - Reconstructing a bibliography from a document with embedded
\begin{thebibliography}or numbered references - Converting a reference list from any format into BibTeX
When NOT to Use
- You already have a
.bibfile and just need to validate it — use the configured bibliography validator - Finding new references on a topic — use an installed literature workflow or scholarly search
- The PDF is already in Paperpile — export via
paperpile export-bibinstead (faster, more accurate)
Input
A single PDF file path. The PDF should contain a bibliography, reference list, or works cited section.
Output
A .bib file, located by context:
- PDF inside a research project (e.g.
articles/,paper-*/, project root) — write to the same directory as the input PDF, namedreferences.bib(per project convention). Ifreferences.bibalready exists, ask before overwriting — offer to merge or use a different name (e.g.,extracted-refs.bib). - Standalone PDF (ad-hoc extraction with no project home — e.g. a client-managed upload) — write to
~/vault/parsed-bibs/<slug>.bib, where<slug>describes the source (e.g.kasberger-algorithmic-cooperation-geb-2026.bib). This is the standing location for one-off parses (established 2026-06-14). Create the folder if absent.
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.
- 1mo ago First seen · 295 lines · 54 tokens per session scan A 9543a2e58aae
bib-parse is a skill published in the GitHub repository flonat/flonat-research (147 stars, last pushed 20d ago), licensed MIT. It adds 54 tokens to every session and 3,743 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
latex-compile
Compile a LaTeX document and fix every error plus aesthetic issue (overfull/underfull boxes, widows, alignment, fonts) for a clean PDF and log. Use this instead of running pdflatex/latexmk manually — it avoids the latexmk stale-log trap and silent grep failures on binary log output, and it reformats rather than…
paper-figures
Extract figures from downloaded papers and include them in survey/review reports. Use when the report covers other groups' work and benefits from their architecture diagrams, experimental plots, or system schematics. Your brain prompt supplies the absolute path to the extract-figures script as {{EXTRACTFIGURES}} — use…
fin-paper-convert
Compile LaTeX to PDF and convert to target journal format.
epd-parser
Extract GWP, life-cycle stages, certifications, and impact metrics from an EPD PDF. Use when given a declaration to parse; not to find or compare EPDs.
lighting-report-extract
Check reported lighting quantities and results in supplied simulation PDFs without adding repeated calculation surfaces. Use for scoped luminaire inventories and illuminance results; not simulation or compliance.
beamer-presentation
Create academic presentations in Beamer with professional themes.