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 Stepkar2004/init-configurator --skill workflowgit clone --depth 1 https://github.com/Stepkar2004/init-configuratorWrote 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/stepkar2004/init-configurator/workflow)<a href="https://agentmods.dev/skills/stepkar2004/init-configurator/workflow"><img src="https://agentmods.dev/badge/skills/stepkar2004/init-configurator/workflow/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/stepkar2004/init-configurator/workflow"><img src="https://agentmods.dev/badge/skills/stepkar2004/init-configurator/workflow.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.00137 | $0.00874 |
| Opus 5.5 | $0.00055 | $0.00350 |
| Sonnet 5.5 | $0.00027 | $0.00175 |
| Haiku 4.5 | $0.00014 | $0.00087 |
Grade A, and why
workflow 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 2mo 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 — 52 lines — stays where its author put it; the contents beside it link to each section on GitHub.
workflow — the loop every implementation session runs
One skill fires for all SWE work; the less-common parts load lazily from
references/when their trigger row matches. Do not rely on separate sibling skills auto-triggering for scale or rot-check — this file is their front door.
The loop
- Orient. Read
docs/state/now.md, then the active plan (docs/plans/when the repo keeps phase plans, else the current chunk indocs/state/roadmap.md). Know the chunk's goal and acceptance criteria before touching code. If no chunk is defined, defining one IS the first task. - Plan the chunk. Smallest end-to-end slice; name the files to touch and the tests that will prove it. If scope grows mid-chunk beyond the plan, stop — re-plan or split; never "just keep going".
- Implement. Follow the constitution (CLAUDE.md) and the architecture rules in the active plan — they are constraints, not suggestions.
- Verify — the forgettable steps, in order:
- New behavior ⇒ new test; changed behavior ⇒ changed test. Same chunk, no IOUs.
- Run the repo's gates:
project.yamldeclares them as tasks; the constitution (CLAUDE.md) and the pre-commit / CI configs are the full set. - User-visible behavior ⇒ actually run it — a green unit test is not a seen behavior.
- Document in the same chunk. Update whatever the change made stale: README, the
plan doc, an ADR for any new decision (
docs/decisions/), docstrings. The test: "would a fresh session mis-learn anything if it read the docs right now?" - Commit at the chunk boundary. Gates green →
docs/state/now.md+log.mdupdated → commit. NEVER push. The user pushes, or explicitly says push — this repo is public; an unpushed mistake is free, a pushed one is not. - Reflect — do not skip, do not defer. Ask it literally: did a lesson land this chunk
(a root cause found, a tool swapped, a convention decided, a default overridden, a
mistake repeated)? If yes, run the evolve procedure NOW
(
skill-manager/references/evolve.md) before the session ends — a lesson you plan to record "later" is a lesson lost, and re-teaching it next session is the tax. Task matched no skill? → one line indocs/state/miss-log.md, keep working.
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.
- 2mo ago First seen · 52 lines · 137 tokens per session scan A 97cdfa114418
workflow is a skill published in the GitHub repository Stepkar2004/init-configurator (1 stars, last pushed 3mo ago), licensed MIT. It adds 137 tokens to every session and 874 once invoked, about $0.0005 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-08-31.
Other skills, from other repositories
chief-data-officer-advisor
Chief Data Officer advisory for startups: AI training data rights and consent provenance, data product strategy (warehouse vs lakehouse vs mesh, build-vs-buy), B2B customer-data-as-asset valuation and M&A readiness, data team org evolution. Use when deciding whether to train models on customer data, choosing data…
general-counsel-advisor
General Counsel advisory for startups: contract review (MSA, SaaS, NDA, DPA, employment), IP strategy, term sheet decoding, and regulatory landscape mapping. Use when reviewing any contract or term sheet, deciding when to engage outside counsel, defining IP strategy, evaluating regulatory exposure (HIPAA, GDPR, FDA…
strategic-alignment
Cascades strategy from boardroom to individual contributor. Detects and fixes misalignment between company goals and team execution. Covers strategy articulation, cascade mapping, orphan goal detection, silo identification, communication gap analysis, and realignment protocols. Use when teams are pulling in different…
wrap-up
Close out a launched Claude Managed Agent — recap every primitive the founder now owns, regenerate the single-file overview page, and suggest the next 1-2 upgrades. Use when the user says "wrap up", "close this out", "what do I own now", "give me the summary", "recap the agent", or when the orchestrator routes…
ma-playbook
M&A strategy for acquiring companies or being acquired. Due diligence, valuation, integration, and deal structure. Use when evaluating acquisitions, preparing for acquisition, M&A due diligence, integration planning, or deal negotiation.
intl-expansion
International market expansion strategy. Market selection, entry modes, localization, regulatory compliance, and go-to-market by region. Use when expanding to new countries, evaluating international markets, planning localization, or building regional teams.