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/vijayjoshi24/ea-agent-skills/presentgit clone --depth 1 https://github.com/vijayjoshi24/ea-agent-skillsWrote 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/vijayjoshi24/ea-agent-skills/present)<a href="https://agentmods.dev/commands/vijayjoshi24/ea-agent-skills/present"><img src="https://agentmods.dev/badge/commands/vijayjoshi24/ea-agent-skills/present.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.00000 | $0.00342 |
| Opus 5 | $0.00000 | $0.00171 |
| Sonnet 5 | $0.00000 | $0.00068 |
| Haiku 4.5 | $0.00000 | $0.00034 |
Grade A, and why
present 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.
What it actually says
/present
Transform technical architecture into stakeholder-ready communication — executive narratives, board slides, business cases, and one-pagers.
When to use
Preparing for CIO/CTO briefings, board presentations, investment proposals, programme steering committees, or vendor strategy communications.
What it produces
- Executive narrative (200–400 words, business language, no jargon)
- Slide structure outline (titles + key point per slide)
- One-pager summary with problem, approach, outcomes, ask
- Business case framing (investment, expected value, risk of inaction)
How to invoke
/present
Then describe what needs presenting:
/present
Summarise our cloud migration strategy for the board. Key points:
we're moving from on-prem to Azure over 3 years, starting with
dev/test environments, estimated cost saving of $2M by year 3,
main risk is skills gap in the infrastructure team.
/present exec
Turn this tech debt assessment into a 5-minute CIO briefing.
[Paste assessment or summary]
/present slides
Create a slide structure for our EA strategy presentation.
Audience: EVP Technology and business unit leaders.
Tone principles
- Lead with business impact, not technical detail
- Frame debt and risk in terms of delivery velocity and cost
- Use outcomes language: "enables", "reduces", "accelerates", "protects"
- One idea per slide — never more than 5 bullet points on any slide
Activates skill
skills/capability-map/ (for landscape views) + inline presentation logic
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 · 52 lines · 0 tokens per session scan A cd526f4f4cd7
present is a command published in the GitHub repository vijayjoshi24/ea-agent-skills (5 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 342 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
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.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.