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 venue-guidelines-compliancegit 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/venue-guidelines-compliance)<a href="https://agentmods.dev/skills/flonat/flonat-research/venue-guidelines-compliance"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/venue-guidelines-compliance/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/venue-guidelines-compliance"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/venue-guidelines-compliance.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00060 | $0.02332 |
| Opus 5 | $0.00030 | $0.01166 |
| Sonnet 5 | $0.00012 | $0.00466 |
| Haiku 4.5 | $0.00006 | $0.00233 |
Grade A, and why
venue-guidelines-compliance 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 8d 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 — 205 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Venue guidelines compliance
Check one active paper and submission package against one precisely scoped set of official venue requirements. Produce an evidence-bound report and a canonical review-state row. Never edit the manuscript, bibliography, guideline evidence, project metadata, or submission files.
Inputs
Accept a paper path or infer it from the current project. Optional arguments may specify:
--venue <venue-slug>;--guidelines <path-or-url>for an explicit guide or official instruction source;--official-source <url>for an additional official source (repeatable);--stage initial|revision|camera-ready;--paper-onlyto exclude portal-only and package-only requirements;--trigger <orchestrator>when invoked by another workflow.
If several paper-* directories exist, require an explicit paper. If the venue, article/content type, track, cycle, or submission stage is ambiguous, ask in an interactive standalone run. In a non-interactive or orchestrated run, record INCOMPLETE; never guess.
Output contract
Write the report to:
reviews/<paper-slug>/venue-guidelines-compliance/<YYYY-MM-DD-HHMM>.md
Use a timestamp or same-day descriptor for every rerun; never overwrite a prior report. Treat the paper and venue materials as read-only. Apart from standard out/ build artifacts created by latex, writing the dated report and appending its reviews/INDEX.md event are the only project mutations.
Workflow
1. Resolve the active paper and venue
Read the project's native guidance, current focus/handoff, paper wrapper, and canonical venue/submission records before exploring files. Resolve:
- project root and paper slug;
- active LaTeX driver and rendered PDF;
- canonical venue slug and venue title;
- official article/content type, track, cycle, and stage;
- whether review is double-blind, single-blind, or non-blind.
Do not use a backup, frozen submission, alternate paper, or stale mirror when a live driver exists. In a multi-paper project, keep every report and INDEX row scoped to the selected paper.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 8d ago First seen · 205 lines · 60 tokens per session scan A 6a583f296da2
venue-guidelines-compliance is a skill published in the GitHub repository flonat/flonat-research (133 stars, last pushed 17d ago), licensed MIT. It adds 60 tokens to every session and 2,332 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
fin-paper-convert
Compile LaTeX to PDF and convert to target journal format.
fin-paper-plan
Generate structured paper outline adapted to target journal.
doc-audit
Evaluate one project document in detail — a workbook section, big picture, strategy map, handoff message, paper, brief, or primer — without editing it. Runs the mechanical lint, builds a claim ledger, types every headline against the eight claim statuses in CLAUDE.md, traces cited evidence to the scripts and logs that…
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…
claim-audit
Audit what a passing script actually established, before writing any prose about it — build the computed-object ledger, rewrite every check's label as the weakest statement that makes its body pass, and separate the verdict on someone else's work from your own new claim. Run after the script passes and BEFORE the…
nb-to-wolfbook
Convert Mathematica .nb or .m files to Wolfbook .wb format so they open and run in VS Code. Use when bringing existing .nb/.m files into Wolfbook, or to make an existing .wb bridge-safe.