Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add V-Songbird/foreman/plugin install 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/survey)<a href="https://agentmods.dev/skills/v-songbird/foreman/survey"><img src="https://agentmods.dev/badge/skills/v-songbird/foreman/survey/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/v-songbird/foreman/survey"><img src="https://agentmods.dev/badge/skills/v-songbird/foreman/survey.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00156 | $0.04993 |
| Opus 5 | $0.00078 | $0.02497 |
| Sonnet 5 | $0.00031 | $0.00999 |
| Haiku 4.5 | $0.00016 | $0.00499 |
Grade A, and why
survey 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 9d 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 — 349 lines — stays where its author put it; the contents beside it link to each section on GitHub.
foreman:survey — ground-truth the roadmap's near-term candidates
This is the one Foreman flow that deliberately investigates the codebase
against the roadmap. foreman:roadmap's pick-next-task branch explicitly
does not do this — see the 0.4.4-alpha changelog entry, where doing
exactly this at pick time burned ~100k tokens on every invocation. Keeping
it a separate, explicitly-triggered skill is what makes both halves cheap:
the fast path stays mechanical, and ground-truthing only runs when someone
actually asks for it.
All reads/writes to ROADMAP.jsonl go through
${CLAUDE_PLUGIN_ROOT}/scripts/roadmap.js — never Read/Edit the file
directly — run it with --help for the command shapes. Read the Fields
section of ${CLAUDE_PLUGIN_ROOT}/roadmap-schema.md for field semantics.
Pre-check: if ROADMAP.jsonl doesn't exist at the project root, tell
the user to run /foreman:init first and stop here.
1. Pick the scope
If a caller handed over a set of ids, that set is the scope — args naming
specific tasks, or Reconcile and pick's near-term set (foreman:roadmap's
pick branch derives it from one next-candidates --menu result: the candidate
rows plus the in_progress and awaiting_acceptance rows). Run list --ids <those ids>, drop any that don't exist or are terminal
(done/dropped/rejected — history its commits already describe) and say
which you dropped, and skip the next-candidates call below. Scoping decides
which entries get investigated and nothing else: steps 2–4 run exactly as
written, on whatever the scope holds. Otherwise:
node ${CLAUDE_PLUGIN_ROOT}/scripts/roadmap.js next-candidates
(default --limit 3) — candidates already include each one's own
depends_on, no separate call needed just to get that.
Survey the top candidates only — same 3 by default as foreman:roadmap
shows. This is deliberately not the whole backlog: a hidden dependency or
stale claim matters most for what's about to be picked, and checking every
planned entry every time would make this as expensive as the thing it's
trying to avoid. If total_unblocked is larger than what you surveyed,
say so when reporting back — don't imply full coverage silently.
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.
- 9d ago First seen · 349 lines · 156 tokens per session scan A c3d91f603858
survey is a skill published in the GitHub repository V-Songbird/foreman (34 stars, last pushed 3d ago), licensed MIT. It adds 156 tokens to every session and 4,993 once invoked, about $0.0008 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
happiness-skill
A Chinese-language guide to happiness based on reducing unmet wants, focusing on the present, and treating happiness as a trainable skill.
session-deep-dive
Deep qualitative analysis of high-signal sessions. Spawns subagents with v2 template, synthesizes patterns, compares against known findings. Use after /session-scan.
brainstorm
Brainstorm Elixir/Phoenix features — explore ideas, compare approaches, gather requirements. Use when vague idea, not sure how to approach, or want to discuss before plan.
elixir-idioms
OTP/BEAM patterns and Elixir idioms — GenServer, Supervisor, Task, Registry, pattern matching, with chains, pipes. Use when designing processes or debugging BEAM issues.
security
Enforce Elixir/Phoenix security — auth, OAuth, sessions, CSRF, XSS, SQL injection, input validation, secrets. Use when editing auth files, login flows, RBAC, or API keys.
tidewave-integration
Tidewave MCP runtime tools — debugging, smoke testing, live state inspection, SQL queries, hex docs. Use when evaluating code in a running Phoenix app.