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/v-songbird/foreman/initnpx skills add V-Songbird/foreman --skill initgit clone --depth 1 https://github.com/V-Songbird/foremanWrote 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/v-songbird/foreman/init)<a href="https://agentmods.dev/skills/v-songbird/foreman/init"><img src="https://agentmods.dev/badge/skills/v-songbird/foreman/init.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.00079 | $0.02763 |
| Opus 5 | $0.00039 | $0.01381 |
| Sonnet 5 | $0.00016 | $0.00553 |
| Haiku 4.5 | $0.00008 | $0.00276 |
Grade A, and why
init 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 — 231 lines — stays where its author put it; the contents beside it link to each section on GitHub.
foreman:init — bootstrap a project roadmap
Creates ROADMAP.jsonl and .foreman/config.json at the project root. Both
are committed to git — they're a shared project artifact, not personal
state. All reads/writes go through
${CLAUDE_PLUGIN_ROOT}/scripts/roadmap.js (see "Write phase" below) — it
enforces the write invariants (id computation, parse-before/after-write)
mechanically, so you don't have to. Run it with --help for the command
shapes; read the Fields section of
${CLAUDE_PLUGIN_ROOT}/roadmap-schema.md if you need field semantics
beyond what's obvious from the names (why/what/depends_on/planned_touches).
If args were provided, treat them as the project description seed and skip asking for it in Call 1.
Trial log. Setup is one of the flows no script can see from outside, so
these lines are the only record it left. Each is a no-op unless the project
set trialLog, so none needs a check first and it never blocks the flow.
At the first question actually put to the user — the Pre-check's Q1 below on a project that already has a roadmap, Call 1's Q1 otherwise — one line:
node ${CLAUDE_PLUGIN_ROOT}/scripts/trial-log.js init_started '{}'
and, after every AskUserQuestion call in this skill, one event per call:
node ${CLAUDE_PLUGIN_ROOT}/scripts/trial-log.js question_asked '{"flow":"init"}'
A Pre-check Cancel therefore leaves an init_started with no
init_completed. That is the correct record of an abandoned setup, not a
gap to paper over.
Pre-check
If ROADMAP.jsonl already exists at the project root, ask before doing
anything else:
Q1 — "ROADMAP.jsonl already exists. What do you want to do?"
Options: Overwrite it (start fresh — discards done entries and their accumulated notes), Keep it, just add to it, Cancel
- Overwrite → continue to Call 1, the draft phase replaces the file.
- Keep, add to it → skip straight to the draft phase, append new entries
instead of replacing, don't touch
.foreman/config.jsonif it already exists (write the defaults below only if the config file is missing). - Cancel → stop here.
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 · 231 lines · 79 tokens per session scan A 740212502a4a
init is a skill published in the GitHub repository V-Songbird/foreman (34 stars, last pushed 4d ago), licensed MIT. It adds 79 tokens to every session and 2,763 once invoked, about $0.0004 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-08-30.
Other skills, from other repositories
compress
Prompt-Studio memory compressor. Shrinks CLAUDE.md, todo lists, and preference files into Prompt-Studio's lean format to cut input tokens on every load. Preserves all technical substance, code, URLs, and structure. Compressed output overwrites the original; human-readable backup stored out-of-tree as FILE.original.md…
lean-commit
Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes…
lean-gain
Show Lean's measured impact as a compact scoreboard: less code, more speed, from the benchmark medians. One-shot display, not a persistent mode, and not a per-repo number. Trigger: /lean-gain, "lean gain", "what does lean save", "show lean impact", "lean scoreboard".
fellowship
Multi-task orchestrator. Coordinates agent teammates (led by Gandalf) running /quest (code) or /scout (research) workflows. Use when you have multiple independent tasks to run in parallel.
quest
Use for any non-trivial task. Orchestrates the Research-Plan-Implement cycle with compaction between phases, integrating council, lembas, gather-lore, and warden. Enforces discipline and phase gates.
retro
Post-fellowship retrospective analysis. Collects gate history, palantir alerts, and quest metrics to surface patterns and interactively recommend configuration improvements.