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 ideasgit 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/ideas)<a href="https://agentmods.dev/skills/flonat/flonat-research/ideas"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/ideas.svg" alt="Measured on agentmods" 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.00032 | $0.01350 |
| Opus 5 | $0.00016 | $0.00675 |
| Sonnet 5 | $0.00006 | $0.00270 |
| Haiku 4.5 | $0.00003 | $0.00135 |
Grade A, and why
ideas 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 4d 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 — 155 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ideas: Capture & Integrate
An inbox for improvement ideas — the gap between
[LEARN]tags (immediate corrections) andskill-extract(full skill creation). Captures raw improvement ideas and periodically integrates the best ones into the system.
Two Modes
| Mode | Trigger | What it does |
|---|---|---|
| Capture | ideas capture [text] |
Append a structured idea entry to log/ideas.md |
| Integrate | ideas integrate |
Review unprocessed ideas and turn them into actions |
Mode 1: Capture
With argument: ideas capture [text]
Parse the text and append a structured entry to log/ideas.md.
Without argument: ideas capture
Ask interactively:
- "What's the idea?" (free text)
- "Where did this come from?" (current session / external repo / user feedback / reading)
Entry Format
## [YYYY-MM-DD] [category] Idea title
- **Quality:** [high] | [medium]
- **Source:** [session | external:repo-name | user-feedback | reading:source]
- **Proposed action:** One-sentence description of what to do
- **Details:** [the idea text, expanded if needed]
- **Status:** unprocessed
Auto-Classification
Classify each idea into one of these categories based on content:
| Category | Signal words / patterns |
|---|---|
[skill-design] |
"new skill", "workflow for", "automate", "slash command" |
[rule] |
"always", "never", "enforce", "prevent", "require" |
[workflow] |
"process", "steps for", "how to handle", "protocol" |
[infrastructure] |
"hook", "MCP", "settings", "permissions", "symlink" |
[research] |
"method", "analysis", "paper", "experiment", "data" |
Quality Rating
| Rating | Criteria |
|---|---|
[high] |
Specific, actionable, addresses a known friction point or recurring issue |
[medium] |
Interesting but needs more thought, or addresses a minor convenience issue |
Skip [low] ideas — if it's not worth recording, don't record it.
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.
- 4d ago First seen · 155 lines · 32 tokens per session scan A e730023beeb2
ideas is a skill published in the GitHub repository flonat/flonat-research (132 stars, last pushed 13d ago), licensed MIT. It adds 32 tokens to every session and 1,350 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.
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…
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.
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…