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 skills/flonat/flonat-research/init-projectnpx skills add flonat/flonat-research --skill init-projectgit 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/init-project)<a href="https://agentmods.dev/skills/flonat/flonat-research/init-project"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/init-project.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 | $0.00032 | $0.00937 |
| Opus 5 | $0.00016 | $0.00468 |
| Sonnet 5 | $0.00006 | $0.00187 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
init-project 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 yesterday.
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 — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Init Project — Research Project Scaffolder
Interactive project setup: answer questions, get a ready-to-use research project directory.
Protocol
Phase 1: Interview
Ask the user these questions using AskUserQuestion (adapt based on what's already known):
- Project name — short name for the directory (e.g.,
nudge-experiment) - Paper title — working title for the paper
- Research question — one sentence
- Target journal/venue — where you plan to submit
- Co-authors — names and affiliations (if any)
- Parent directory — where to create the project (default:
~/Research/) - Overleaf path — path to Overleaf-synced directory for symlink (optional)
- Methodology — experimental, observational, theoretical, simulation, mixed
Phase 2: Scaffold
Create the directory structure:
<project-name>/
├── CLAUDE.md # Project-specific Claude instructions
├── README.md # Project overview
├── MEMORY.md # Knowledge base (seeded with template)
├── paper/ # → Overleaf symlink (or empty dir)
├── code/
│ ├── python/ # Python scripts
│ └── R/ # R scripts
├── data/
│ ├── raw/ # Original data (never modified)
│ └── processed/ # Cleaned/transformed data
├── results/ # Analysis outputs
├── figures/ # Generated figures
├── docs/ # Project documentation
├── correspondence/ # Referee reports, cover letters
│ └── referee2/ # Referee 2 agent reports
├── log/ # Session logs
│ └── plans/ # Saved plans
└── .gitignore
Phase 3: Populate Files
CLAUDE.md — project-specific instructions:
- Paper title and research question
- Co-authors and target venue
- Methodology and key conventions
- Pointer to project context files
README.md — human-readable overview:
- Project title and description
- Directory structure explanation
- How to compile the paper
- Co-author information
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.
- yesterday First seen · 116 lines · 32 tokens per session scan A 984851ba7e9a
init-project is a skill published in the GitHub repository flonat/flonat-research (131 stars, last pushed 10d ago), licensed MIT. It adds 32 tokens to every session and 937 once invoked, about $0.0002 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.
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…
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…
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.