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/bricerising/enterprise-software-playbook/workflownpx skills add bricerising/enterprise-software-playbook --skill workflowgit 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/workflow)<a href="https://agentmods.dev/skills/bricerising/enterprise-software-playbook/workflow"><img src="https://agentmods.dev/badge/skills/bricerising/enterprise-software-playbook/workflow.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.1 | $0.00076 | $0.02768 |
| Opus 5 | $0.00038 | $0.01384 |
| Sonnet 5 | $0.00015 | $0.00554 |
| Haiku 4.5 | $0.00008 | $0.00277 |
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 6d 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 — 201 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Workflow (Auto Router)
Overview
This skill is a workflow orchestrator: it routes work across the other skills in this repo so you can deliver cohesive enterprise web app changes without the user needing to micromanage “which skill to use”.
Default loop: Define → Standardize → Harden → Verify.
Chooser
- Use workflow when: the user gives a general request ("add feature X", "fix this bug", "refactor module Y") without naming a specific skill. Workflow picks the right skills and sequences them.
- Do NOT use workflow when: the user names a specific skill ("run plan", "write a spec", "do a review") — invoke that skill directly.
- Do NOT use workflow for: one-shot questions about code, explanations, or small edits that don't need multi-skill orchestration.
Inputs / Outputs
Inputs: User request (unstructured), codebase.
Outputs: Completed work via orchestrated skill chain; final output from the last skill (typically finish for non-trivial changes).
Workflow
0) Calibrate scope (keep overhead proportional)
Classify the request:
- Tiny change: small UI copy tweaks, rename a local variable, fix a typo. No behavior/contract change.
- Normal change: touches behavior, boundary semantics, or adds a feature.
- Big change: cross-service work, migrations, or changes that affect multiple boundaries/teams.
For this repo, non-trivial = normal or big.
Rule: only create/expand specs and platform primitives when they reduce future drift for the expected scope.
Proportionality guide (what to skip per scope):
| Scope | Skip | Always apply | Use if relevant |
|---|---|---|---|
| Tiny | plan, spec, architecture, design, platform, review, finish |
typescript (if TS) |
testing (if behavior changed) |
| Normal | architecture (unless cross-service), platform (unless 2+ services) |
plan, archobs, testing, finish |
spec (if contracts change), resilience/security/observability (if I/O touched) |
| Big | nothing | plan, archobs, spec, testing, finish |
all Harden + Standardize skills |
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.
- 6d ago First seen · 201 lines · 76 tokens per session scan A fd17f7d5309d
workflow is a skill published in the GitHub repository bricerising/enterprise-software-playbook (7 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 76 tokens to every session and 2,768 once invoked, about $0.0004 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
replit-deck
For product and technical management work: turn PRDs, roadmaps, RFCs, architecture reviews, and retros into decision documents. Built around the core query "pm-feature-business-case-deck", with product strategy lead judgment, buyer-ready proof, and this outcome: approve the feature, architecture, roadmap, or incident…
hps-true-blueprint
OpenDesign's engineering blueprint: how the sandbox, sidecar, and daemon fit — the system diagram and the invariants. Built as a decision-grade product management deck for engineering org.
html-ppt-knowledge-arch-blueprint
OpenDesign's incident retro: the daemon-restart data bug, the root cause, the fix, and the systemic follow-ups. Built as a decision-grade product management deck for engineering, SRE, leadership.
deck-open-slide-canvas
OpenDesign's architecture review: the local daemon + agent-runtime design, the tradeoffs, and the decision to lock. Built as a decision-grade product management deck for staff eng, tech leads, security.
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…