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 bricerising/enterprise-software-playbook --skill plangit clone --depth 1 https://github.com/bricerising/enterprise-software-playbookWrote 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/bricerising/enterprise-software-playbook/plan)<a href="https://agentmods.dev/skills/bricerising/enterprise-software-playbook/plan"><img src="https://agentmods.dev/badge/skills/bricerising/enterprise-software-playbook/plan/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/bricerising/enterprise-software-playbook/plan"><img src="https://agentmods.dev/badge/skills/bricerising/enterprise-software-playbook/plan.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.00066 | $0.01870 |
| Opus 5.5 | $0.00026 | $0.00748 |
| Sonnet 5.5 | $0.00013 | $0.00374 |
| Haiku 4.5 | $0.00007 | $0.00187 |
Grade A, and why
plan 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 1mo 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 — 129 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Plan
Overview
Create a short plan that a developer (or agent) can execute end-to-end: ordered tasks, acceptance checks, and a concrete verification strategy.
Chooser
- Use plan when: starting non-trivial work that needs task ordering, risk flags, or cross-cutting coordination — especially when scope is ambiguous or multiple approaches exist.
- Do NOT use plan when: the change is tiny (rename, typo fix, single-file edit) — just do it.
- Do NOT use plan for: writing spec artifacts or contracts (use
spec); auto-routing across multiple skills (useworkflow).
Inputs / Outputs
Inputs: User request; archobs JSON from archobs show all --format json (required for non-tiny); forecast data (if external dependencies involved via step 4b).
Outputs: Objective function, decision table (if 2+ approaches), ordered task list with acceptance criteria, measurement ladder. Consumed by downstream skills: spec, architecture, design, testing, finish.
Workflow
- Write the objective function:
- goal (one sentence)
- constraints (budget/time/compliance/latency/team capacity/etc.)
- anti-goals (what you are explicitly not optimizing now)
- Externalize a one-page system sketch:
- boundary (in/out) + time horizon (near-term vs later)
- actors + incentives
- key flows (work/data/risk/attention)
- top 3 constraints/bottlenecks
- Scope the change:
- impacted components/services
- impacted boundaries/contracts (HTTP/gRPC/events/WS/data model)
- what is explicitly out of scope
- Load archobs data (required): Run
archobs show all --format jsonto get risk scores, cluster health, and drift in one shot. Files withrisk > 0.5and clusters withleakage > 0.20should appear earlier in the task order. Drift data (ari_prev < 0.50) flags areas to avoid broad moves in. If the artifacts do not exist, runarchobs report --repo <path> --out .archobs --suggestions-provider rulesand wait for it to complete before continuing. 4b. Risk Amplification (conditional — run when any high-risk files/clusters from archobs touch external dependencies or technology choices):
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.
- 1mo ago First seen · 129 lines · 66 tokens per session scan A 464ec14098b0
plan is a skill published in the GitHub repository bricerising/enterprise-software-playbook (8 stars, last pushed 7d ago), licensed Apache-2.0. It adds 66 tokens to every session and 1,870 once invoked, about $0.0003 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
architecture-aware-init
Selects architecture paradigm via research before scaffolding. Use when architecture is undecided and the choice needs justification and documentation.
frontmcp-guides
Tutorials, end-to-end walkthroughs, and complete reference projects for FrontMCP. Use when you want a getting-started guide, a full worked example, or to learn best practices by following a step-by-step build rather than a single API reference. Includes a beginner weather-API server (tool plus static resource, Zod…
analiz-html-report
Use when you write or revise the analiz deliverable - the ONE self-contained HTML report (spec and plan as sections) a human reviews passage by passage.
release
Guide through the Cortex TMS release process — version bump, changelog, sync, tag, publish. Every step requires user approval.
analiz-human-review-gate
Use when you finish an analiz report - the human must approve the analysis before any implementation task is created, via the analizreview column.
game-engine-choice
Use when a game task could run on more than one engine or the repository has no engine yet - read the repo's engine and pinned version, and only for a brand-new game pick one from platforms, 2D/3D, team language, scale and licensing.