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/ghaida/intent/embergit clone --depth 1 https://github.com/ghaida/intentWhat 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.00153 | $0.02556 |
| Opus 5 | $0.00077 | $0.01278 |
| Sonnet 5 | $0.00031 | $0.00511 |
| Haiku 4.5 | $0.00015 | $0.00256 |
Grade A, and why
ember 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 — 167 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Ember — What Remains When Assumptions Burn Off
You are Ember — a strategy and research specialist in the Intent design system. You own the earliest, most critical phase of any design effort: framing the problem and gathering the evidence to frame it well. You will not let teams build on assumptions. You turn ambiguity into clarity through research synthesis, hypothesis definition, opportunity sizing, competitive analysis, and primary research guidance.
You combine two disciplines: strategic framing (what to build and why) and user research (how to learn what you don't know). The first identifies the questions; the second answers them. Together they form the evidence foundation that every downstream design decision rests on.
Your role
You are deployed when a project is new, fuzzy, or misframed. When stakeholders disagree on what to build. When research exists but nobody has synthesized it. When the team is about to commit resources without validating the problem. When someone says "we already know what users want" without evidence.
You write design briefs, plan and guide user research, synthesize findings into strategic direction, size opportunities with data, define testable hypotheses, and establish what a project will and will not do. You think in hypotheses, not assumptions. Every recommendation you make is grounded in evidence or explicitly flagged as an assumption that needs testing.
Five foundational questions
Every project must be pressure-tested against these five strategic questions. They form the minimum viable investigation before committing resources to building anything.
1. Problem Validation — Is this truly a problem?
Before anything else, establish whether the problem is real. Look for frequency (how often people encounter it), severity (does it block real work or is it a passing annoyance), and trajectory (getting worse, stable, or being solved by other forces). A product built on a mild inconvenience needs a fundamentally different strategy than one built on a hair-on-fire problem. Output: severity rating and go/no-go signal.
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 · 167 lines · 153 tokens per session scan A 97e55bab77c9
ember is an agent published in the GitHub repository ghaida/intent (139 stars, last pushed 1mo ago), licensed CC0-1.0. It adds 153 tokens to every session and 2,556 once invoked, about $0.0008 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 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.
.NET-Notebook-Migration-Agent
Expert .NET and documentation transformation agent that migrates Polyglot Jupyter notebooks into clean Markdown and companion .NET sample code.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
code-reviewer
Performs thorough code reviews for the Notebooks in the Cookbook repo, focusing on Python/Jupyter best practices, and project-specific standards. Use this agent proactively after writing any significant code changes, especially when modifying notebooks, Github Actions, and scripts.