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 commands/d-padmanabhan/agent-engineering-handbook/creativegit clone --depth 1 https://github.com/d-padmanabhan/agent-engineering-handbookWrote 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/d-padmanabhan/agent-engineering-handbook/creative)<a href="https://agentmods.dev/commands/d-padmanabhan/agent-engineering-handbook/creative"><img src="https://agentmods.dev/badge/commands/d-padmanabhan/agent-engineering-handbook/creative.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.00010 | $0.00539 |
| Opus 5 | $0.00005 | $0.00269 |
| Sonnet 5 | $0.00002 | $0.00108 |
| Haiku 4.5 | $0.00001 | $0.00054 |
Grade A, and why
creative 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 4d 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 — 109 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CREATIVE MODE ACTIVATED
You are now in CREATIVE phase for design exploration.
When to Use
Required for:
- Level 3-4 complexity tasks
- Architectural decisions
- Multiple valid approaches exist
- Design choices affect multiple components
Your Tasks
-
Identify Design Decisions
- What choices need to be made?
- What constraints exist?
- What are the requirements?
-
Explore Options
- Generate 2-4 viable alternatives
- Don't pre-judge - explore thoroughly
- Consider unconventional approaches
-
Compare Options
- Create comparison table
- Evaluate against requirements
- Consider trade-offs
-
Make Recommendation
- Choose best option with clear rationale
- Document why others were rejected
- Outline implementation approach
-
Document Decision
- Create
creative-*.mdin tmp/ folder - Update
tasks.mdwith design decisions
- Create
Output Format
## Design Decision: [Component/Feature Name]
### Context
[What problem are we solving? What constraints exist?]
### Requirements
1. [Requirement 1]
2. [Requirement 2]
3. [Requirement 3]
### Options Explored
#### Option A: [Name]
**Description:** [How it works]
**Pros:**
- [Pro 1]
- [Pro 2]
**Cons:**
- [Con 1]
- [Con 2]
#### Option B: [Name]
**Description:** [How it works]
**Pros:**
- [Pro 1]
- [Pro 2]
**Cons:**
- [Con 1]
- [Con 2]
### Comparison Matrix
| Criteria | Option A | Option B | Option C |
|----------|----------|----------|----------|
| Performance | ⭐⭐⭐ | ⭐⭐ | ⭐⭐⭐ |
| Simplicity | ⭐⭐ | ⭐⭐⭐ | ⭐ |
| Maintainability | ⭐⭐⭐ | ⭐⭐ | ⭐⭐ |
### Recommendation
**Chosen:** Option [X]
**Rationale:** [Why this option best meets requirements]
**Trade-offs Accepted:** [What we're giving up]
### Implementation Outline
1. [Step 1]
2. [Step 2]
3. [Step 3]
Rules
- Explore thoroughly before deciding
- Document ALL options considered
- Be explicit about trade-offs
- Get user approval before proceeding to
/build(HITL / human-in-the-loop)
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.
- 4d ago First seen · 109 lines · 10 tokens per session scan A d954f3694bba
creative is a command published in the GitHub repository d-padmanabhan/agent-engineering-handbook (16 stars, last pushed 4d ago), licensed MIT. It adds 10 tokens to every session and 539 once invoked, about $0.0001 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-30.
Other commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.