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-forkgit 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-fork)<a href="https://agentmods.dev/skills/flonat/flonat-research/venue-fork"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/venue-fork/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-fork"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/venue-fork.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
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 →
- high Agent Snooping · line 53 Skill reads from agent configuration directories (.claude/, .codex/, .gemini/). These directories may contain API keys, personal settings, and other credentials that the skill has no legitimate need to access.Fix: Remove all code or instructions that access agent configuration directories (.claude/, .codex/, .gemini/). If configuration values are needed, pass them explicitly as parameters or environment variabl
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.00068 | $0.02894 |
| Opus 5 | $0.00034 | $0.01447 |
| Sonnet 5 | $0.00014 | $0.00579 |
| Haiku 4.5 | $0.00007 | $0.00289 |
Grade B, and why
venue-fork scanned grade B with 2 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
`find <new-overleaf-folder> -name .git` is empty. See `.claude/rules/template-scaffold-strip-git.md`. Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
4. **Inbox**: `curl -X POST localhost:8765/api/sync` (Mac Mini) and confirm the notification item How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Venue Fork: Second-Venue Submission Variant
Fork a paper for a second venue while the original submission keeps living. A fork is a copy
(both venues track independently), unlike retarget-journal (a move) and preprint (a
non-archival variant that must NOT get a vault submission entry).
When to Use
- A venue window explicitly permits concurrent submission (e.g. WINE 2026 ⟷ FOCS/SAGT/AFT 2026)
- A rejected paper needs a reformatted version for a differently-formatted venue
- the user says "submit this also to X", "concurrent submission to X", "make the X version"
Phase 0 — CFP compliance sheet (blocks everything)
Fetch the official CFP (never WikiCFP alone; mark-unverified applies) and record:
| Item | Why it matters |
|---|---|
| Page limit + what's excluded (title page? references? appendix policy) | Drives the refit budget in Phase 3 |
| Font size / margins / class requirements | Submission format is often looser than camera-ready (e.g. WINE: ≥11pt, ≥1in, any class; LNCS only at camera-ready) |
| Blind policy | Anonymity QA in Phase 4; third-person self-citation per double-blind-self-citation rule |
| Concurrent policy — on BOTH sides | The target naming the source venue is not enough; verify the source venue's CFP reciprocates |
| Deadlines: submission, rebuttal, notification | Also the SOURCE venue's notification date |
Timing analysis (report to the user): if the source venue notifies before the target's rebuttal/notification, acceptance there forces withdrawal from the target before any reviews arrive — the fork is then insurance + comments-on-rejection, not guaranteed feedback. Say so explicitly before doing the work.
Phase 1 — Create the fork
- New Overleaf project via Dropbox (the active client may create these — folder + main.tex = project):
Apps/Overleaf/Paper {Theme} {Short Name} ({VENUE} {YY})/— Title Case, venue suffix, per the existing naming convention. Resolve the Dropbox root permulti-machine.md. - Copy from the source project:
main.tex, the bib, figure dirs, any.bstthe target format needs. Never edit the source project's files — it is a live submission surface. Copy files by name only — nevercp -ra whole template/source dir into the new Overleaf folder, which would drag a.gitin and make it a repo on the wrong remote. Confirmfind <new-overleaf-folder> -name .gitis empty. See.claude/rules/template-scaffold-strip-git.md. - Project dir:
mkdir <project>/paper-{venue}/+ relative symlinkpaper-{venue}/paper → ../../../../../Apps/Overleaf/<name>(absolute symlinks break cross-machine).
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 · 165 lines · 68 tokens per session scan B 47cc95c3a40b
venue-fork is a skill published in the GitHub repository flonat/flonat-research (133 stars, last pushed 16d ago), licensed MIT. It adds 68 tokens to every session and 2,894 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it B with 2 findings (reads agent configuration directories, makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
buffer-sizing
Calculate project, feeding, and resource buffers — shared with implementation-planning.
leadership
Executive leadership expertise for decision-making, change management, crisis management, stakeholder management, team building, and organizational leadership. Use when leading teams, managing change, navigating crises, or developing leadership skills.
jira-administration
Complete JIRA project and system administration including projects, automation rules, permissions, users, notifications, screens, issue types, and workflows. Use when managing project structure, automating work, configuring team access, or setting up issue tracking.
shared-monorepo-turborepo
Turborepo, workspaces, package architecture, @repo/ naming, exports, tree-shaking.
infrastructure-rules
Skill for the rules module — discovery, validation, scope, and private-sidecar symlink sync for the top-level rules/ directory (specifications include soft markdown guidelines and strong yaml/json formal constraints). Use when discovering rules (discoverrules), resolving a rule path (resolveruleroot), validating rule…
speckit-companion-specify
../../../.specify/extensions/companion/.specify-dev/agent-commands/claude/speckit-companion-specify/SKILL.md.