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 nirecom/agents --skill workflow-initgit clone --depth 1 https://github.com/nirecom/agentsWrote 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/nirecom/agents/workflow-init)<a href="https://agentmods.dev/skills/nirecom/agents/workflow-init"><img src="https://agentmods.dev/badge/skills/nirecom/agents/workflow-init/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/nirecom/agents/workflow-init"><img src="https://agentmods.dev/badge/skills/nirecom/agents/workflow-init.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.00014 | $0.02687 |
| Opus 5.5 | $0.00006 | $0.01075 |
| Sonnet 5.5 | $0.00003 | $0.00537 |
| Haiku 4.5 | $0.00001 | $0.00269 |
Grade A, and why
workflow-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 — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
IMPORTANT: Interactive session required. Hard-fail in non-interactive contexts (claude -p, /loop, subagents).
Purpose
First step of every workflow session. Routes on GH issue context: Path A (#N + intent:clarified) skips interview; Path B (#N, no label) pre-fills interview; Path C (no #N) runs full interview and auto-creates a tracking issue.
Procedure
Read rules/github-issues.md before WI-2 — on-demand-only, never auto-injected; the meta label, intent:clarified, closes_issues insertion order, and the sub-issue open-state gate all come from it.
WI-1 — Resolve <PLANS_DIR>
Canonical: skills/_shared/resolve-plans-dir.md. Substitute the resolved absolute path for every <PLANS_DIR> placeholder below. Subagent prompts must receive literals — they cannot expand $VAR.
WI-2 — Driver loop
The driver (bin/workflow/workflow-init-driver) handles WI-3..WI-9: token detection, gh issue view fetch for each N in ISSUES, CLOSED detection, label extraction, meta classification (meta strip / open sub-issue guard), Aggregate WIP check (all N: all_same / all_none / any_other), route decision, and context.md write. The driver writes the checkpoint and <SID>-context.md directly under PLANS_DIR (outside git repos → ENFORCE_WORKTREE does not apply).
Invocation: node "$AGENTS_MAIN_ROOT/bin/workflow/workflow-init-driver" <raw-tokens> 2>/dev/null
(<raw-tokens> = issue number tokens like #15 or #15 #22 — not the full user prompt)
On resume (after ask_user): node "$AGENTS_MAIN_ROOT/bin/workflow/workflow-init-driver" --resume <CHECKPOINT> --answer '<token>'
Read all KEY=VALUE output lines. Dispatch on ACTION=:
| ACTION | Meaning | What to do |
|---|---|---|
invoke |
Next skill ready | Run NEXT_SKILL via Skill tool |
done |
Driver complete | Proceed to WI-10; follow PATH_DECISION= at WI-12 (Path C still runs WI-10 onward — no jump) |
blocked |
Unrecoverable | Show REASON= + NEXT_HINT= and stop |
ask_user |
User decision needed | Percent-decode OPTIONS_DISPLAY= (encoded like QUESTION=), present via AskUserQuestion; re-invoke with --resume <CHECKPOINT> --answer '<token>' |
emit_sentinel |
Driver requests sentinel | Emit SENTINEL= via separate Bash call |
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 Changed 36739d5d65c2
- 6d ago Changed · -1 lines d023d43d5aef
- 7d ago Changed 61301564679d
- 9d ago Changed · +1 lines a881d607db60
- 11d ago Changed 2c676a77f696
- 17d ago Changed 6383fe7279fa
- 21d ago Changed 01e113b121e9
- 1mo ago Changed · -3 lines e1e73ff32568
- 1mo ago First seen · 102 lines · 14 tokens per session scan A d331eaec165d
workflow-init is a skill published in the GitHub repository nirecom/agents (3 stars, last pushed today), licensed MIT. It adds 14 tokens to every session and 2,687 once invoked, about $0.0001 per session on Opus 5.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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
projects
List all managed projects with status, branch, open PRs, and open issue counts — portfolio-level view.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…