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/unbergant/bergant-workflow/project-initnpx skills add UnBergant/bergant-workflow --skill project-initgit clone --depth 1 https://github.com/UnBergant/bergant-workflowWrote 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/unbergant/bergant-workflow/project-init)<a href="https://agentmods.dev/skills/unbergant/bergant-workflow/project-init"><img src="https://agentmods.dev/badge/skills/unbergant/bergant-workflow/project-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.00129 | $0.02602 |
| Opus 5 | $0.00064 | $0.01301 |
| Sonnet 5 | $0.00026 | $0.00520 |
| Haiku 4.5 | $0.00013 | $0.00260 |
Grade A, and why
project-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 yesterday.
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 — 184 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Project Init
Turns a specification into plan documents. On a repository that already exists, most tasks do
not need this at all — lifecycle adopts the project and runs without a plan document. Reach
for project-init when the deciding has not happened yet, and use --from <phase> to skip the
phases whose answers the project already has.
Routing
status (or no arguments): execute INLINE — read docs/spec-state.json and display the phase table. Do NOT launch an agent. See "Status Display" below.
This skill's directory (its reference files live here) — resolved at runtime: !echo ${CLAUDE_SKILL_DIR}
All other commands (start, complete, recover): launch Agent(general-purpose) with the prompt below. Replace SKILL_DIR with the absolute path printed just above:
Read the project-init skill:
- Commands and rules: SKILL_DIR/SKILL.md (from "## Agent Instructions")
- Phase execution details: SKILL_DIR/references/phases.md (read ONLY the active phase section)
Execute command: $ARGUMENTS
State file: docs/spec-state.json
Project root: !`pwd`
Read existing docs/ artifacts for context before acting.
Follow all instructions. When you hit a user gate, return findings, options, and what needs discussion. Be concise.
If the agent returns an error, display it without re-running.
Status Display
Read docs/spec-state.json. If missing: "No active spec analysis. Use /bergant-workflow:project-init start <spec-file> to begin."
Display formatted table:
- Each phase with status (pending, in_progress, completed)
- Current phase highlighted
- User gates marked
- Next action needed
What ships with it
1 file 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.
- yesterday Changed · +24 lines e86d20259813
- 5d ago First seen · 160 lines · 129 tokens per session scan A b03b3287bdac
project-init is a skill published in the GitHub repository UnBergant/bergant-workflow (5 stars, last pushed 4d ago), licensed MIT. It adds 129 tokens to every session and 2,602 once invoked, about $0.0006 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-31.
Other skills, from other repositories
planflow
Draft a plan and get it approved as an editable flowchart in the user's browser before executing. Use when the user asks to plan a task with PlanFlow, or wants to review, edit, or approve a plan before any code changes are made.
chief-revenue-officer
Owns the revenue engine end to end: sales, monetization, pricing, customer success, retention, and partnerships. Use this for pricing and packaging decisions, sales strategy and coverage, forecast and pipeline health, churn and expansion, partner and channel strategy, or when marketing-sourced demand is not…
chief-strategy-officer
Owns where the business plays and how it wins over a multi-year horizon — portfolio choices, corporate development, strategic partnerships, and planning under uncertainty. Use this for a decision about which markets or businesses to be in, whether to build, buy, or partner, how to allocate capital across business…
financial-statement-analysis
Reads a set of financial statements and establishes what changed and why — fluctuation analysis against prior period and against budget, profitability, liquidity, solvency and efficiency ratios, benchmarking, and the non-GAAP measures presented alongside them. Use this to interpret results, review a counterparty's or…
youtube-producer
Plans, packages, and scripts long-form video for retention and channel growth — idea selection, titles and thumbnails, script structure, and diagnosing why a video or channel underperforms. Use this for video ideas, packaging, scripting, a retention teardown, or channel strategy — including when someone describes a…
scenario-planning
Plans under genuine uncertainty — building scenarios, identifying which assumptions are load-bearing, setting early-warning indicators, and stress-testing a plan against futures rather than forecasting one. Use this when a decision depends on something unknowable, when a plan assumes conditions that may not hold…