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.
git clone --depth 1 https://github.com/varunk130/ai-workflow-playbooksWrote 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/commands/varunk130/ai-workflow-playbooks/construct)<a href="https://agentmods.dev/commands/varunk130/ai-workflow-playbooks/construct"><img src="https://agentmods.dev/badge/commands/varunk130/ai-workflow-playbooks/construct/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/commands/varunk130/ai-workflow-playbooks/construct"><img src="https://agentmods.dev/badge/commands/varunk130/ai-workflow-playbooks/construct.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.00000 | $0.00130 |
| Opus 5.5 | $0.00000 | $0.00052 |
| Sonnet 5.5 | $0.00000 | $0.00026 |
| Haiku 4.5 | $0.00000 | $0.00013 |
Grade A, and why
construct 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.
What it actually says
Run the CONSTRUCT stage of the AI Workflow Playbooks pipeline.
Load and execute these playbooks together:
playbooks/iterative-construction/PLAYBOOK.md- Build in thin vertical slices with continuous verificationplaybooks/test-first-engineering/PLAYBOOK.md- Write tests before implementation code
For each task in the implementation sequence:
- Write a failing test that captures the expected behavior
- Implement the minimum code to make the test pass
- Refactor for clarity while keeping tests green
- Commit after each completed task
Verify all tests pass and no regressions are introduced before marking a task complete.
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 · 14 lines · 0 tokens per session scan A e8ee7b86799f
construct is a command published in the GitHub repository varunk130/ai-workflow-playbooks (2 stars, last pushed 13d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 130 tokens. 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 commands, from other repositories
red-team
Stress-test a plan, strategy, PRD, or launch with a room of hostile expert personas before you commit.
plan-feature
Production-grade feature planning with dual-AI validation (Claude + Antigravity/Gemini 3 via agy).
feature
Take a feature from a one-line description to a reviewed, tested change through a fixed pipeline: orient with the code-explorer agent, clarify requirements, write a task-by-task plan with the writing-plans skill, execute it with test-driven development, simplify with the code-simplifier agent, verify completion, and…
test
/test [optional: specific test file or pattern] /test --coverage /test --watch /test --red-only # Force RED-phase semantics (writes failing tests, no implementation) /test --tdd # Run with TDD enforcement explicitly enabled for this invocation.
retro
/retro [optional: sprint name or date range].
plan-refactor
Plan a refactor as a sequence of safe verified steps, with tests established before anything moves.