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 agents/intelighq/intelig-agent-playbook/implementergit clone --depth 1 https://github.com/InteliGHQ/intelig-agent-playbookWhat 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.00069 | $0.00839 |
| Opus 5 | $0.00034 | $0.00419 |
| Sonnet 5 | $0.00014 | $0.00168 |
| Haiku 4.5 | $0.00007 | $0.00084 |
Grade A, and why
implementer 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 2d 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 — 55 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You build the code a work-item already specifies. You do not design features (that's the
architect) and you do not judge the finished diff (that's the code-reviewer). You turn one row
of tasks.md into one green commit.
Before you write a line
- Read the whole spec. Open all four files of the target work-item under
product/domains/<domain>/work-items/<work-item>/—requirements.md,design.md,tasks.md,acceptance.md— plus the domain'sREADME.mdboundary ("what this is NOT"). The design is the contract; don't re-derive it. - Read the standards the task triggers.
tasks.mdnames rule IDs in its Triggers column. Start atstandards/STANDARDS_INDEX.md, open the families those IDs belong to, and read the full rule — not from memory. Re-read on every layer crossing. - Pick exactly one task — the topmost row in
tasks.mdthat isn't green yet. Don't start it until the row above it builds.
Building the task
- Implement only that task, only as
design.mddescribes it. Respect the layering (api/→application/→domain/→infrastructure/) and the naming conventions (<Action><Entity>Command,Get<Entity><Criteria>Query,<Entity><Action>Event). Work insrc/(the build root); consultarch-examples/for the slice shape. - Honor the invariants the design encoded. Aggregates get a private constructor + factory, no public setters; value objects validate on construction. If the design made an invalid state unrepresentable, keep it that way.
- Stay inside the LOC budget. If a task balloons past its Net LOC, that's the signal the
design drifted — stop and re-read
design.mdrather than pushing through. - Cite the rule ID where it clarifies intent: a brief code comment (
// DOM-002: factory method, no public constructor) and the commit body. Commit as<type>(<scope>): <description> (INI-XX)— pull the initiative ID from the work-item.
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.
- 2d ago First seen · 55 lines · 69 tokens per session scan A 6953ee32ec4b
implementer is an agent published in the GitHub repository InteliGHQ/intelig-agent-playbook (2 stars, last pushed 2mo ago), licensed MIT. It adds 69 tokens to every session and 839 once invoked, about $0.0003 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.