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 retarget-journalgit 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/retarget-journal)<a href="https://agentmods.dev/skills/flonat/flonat-research/retarget-journal"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/retarget-journal/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/retarget-journal"><img src="https://agentmods.dev/badge/skills/flonat/flonat-research/retarget-journal.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, 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 Tool Misuse · line 57 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Excessive Agency · line 123 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.
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.00061 | $0.01743 |
| Opus 5 | $0.00030 | $0.00872 |
| Sonnet 5 | $0.00012 | $0.00349 |
| Haiku 4.5 | $0.00006 | $0.00174 |
Grade A, and why
retarget-journal 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 — 146 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Retarget Journal Skill
Switch a paper manuscript from one journal to another. Handles folder renaming, bibliography swaps, citation key updates, formatting changes, and compilation verification.
When to Use
- Switching a paper's target venue (e.g., Journal A to Journal B, Journal C to Journal D)
- After a rejection when resubmitting to a different journal
- When strategic decisions change the target venue mid-drafting
Before Starting
Ask the user for:
- Current project path — where is the paper?
- Target journal — full name and abbreviation
- What changes? — some retargets are minor (formatting), others are major (restructuring)
Read the project's CLAUDE.md and README.md to understand current state.
Workflow
Phase 1: Assess Scope
Read the current manuscript and compare against the target journal's requirements:
| Check | What to compare |
|---|---|
| Word/page limit | Does the draft fit? Need to cut or can expand? |
| Required sections | Does the target need sections the current draft lacks? (e.g., "Relevance Statement", "AI Disclosure") |
| Citation style | Author-year vs numbered? natbib vs biblatex? |
| Formatting | Template class? Column layout? Font requirements? |
| Supplementary material | Online appendix conventions? |
Present the assessment to the user before proceeding.
Phase 2: Rename and Restructure
-
Rename project folder if it references the old journal:
mv "old-journal-name/" "new-journal-name/" -
Update Overleaf symlink if one exists:
# Remove old symlink rm paper/ # Create new symlink to the correct Overleaf directory ln -s "/path/to/Overleaf/new-project" paper -
Update folder references in
CLAUDE.md,README.md,.gitignore
Phase 3: Bibliography
- Swap
.bibfile if the user provides a new export from Paperpile - Update citation keys across all
.texfiles:- Read the new
.bibto get the new key format - Find all
\cite{...},\citet{...},\citep{...},\citeauthor{...}commands in.texfiles - Map old keys to new keys (match by author + year)
- Replace all occurrences
- Read the new
- Validate — cross-reference every manuscript citation key against the
.bibfiles and report missing or unused keys. Use an installed bibliography validator for deeper metadata checks when available.
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 · 146 lines · 61 tokens per session scan A af256b0cb7f3
retarget-journal is a skill published in the GitHub repository flonat/flonat-research (133 stars, last pushed 16d ago), licensed MIT. It adds 61 tokens to every session and 1,743 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.