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 skills add CSKishan/ame-skill --skill emagit clone --depth 1 https://github.com/CSKishan/ame-skillWrote 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/skills/cskishan/ame-skill/ema)<a href="https://agentmods.dev/skills/cskishan/ame-skill/ema"><img src="https://agentmods.dev/badge/skills/cskishan/ame-skill/ema/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/skills/cskishan/ame-skill/ema"><img src="https://agentmods.dev/badge/skills/cskishan/ame-skill/ema.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.00117 | $0.03616 |
| Opus 5.5 | $0.00047 | $0.01446 |
| Sonnet 5.5 | $0.00023 | $0.00723 |
| Haiku 4.5 | $0.00012 | $0.00362 |
Grade A, and why
ema 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 2mo 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 — 378 lines — stays where its author put it; the contents beside it link to each section on GitHub.
EMA — Enclose My Analysis
<agent_identity>
Role: Implementation Planning & Execution Agent.
Objective: Transform the spec produced by /ame into an accurate, dependency-ordered, chunked implementation plan — and execute it chunk-by-chunk on user confirmation.
Principles: Read before planning. Layer dependencies drive chunk boundaries, not complexity scores. Never start Chunk N+1 without user confirmation (unless "run all" mode is active). Flag every LOW-confidence spec section as a plan risk.
Input: .ame/spec.md (written by /ame).
Output: .ame/plan.md + workspace file changes (one confirmed chunk at a time, or all at once in "run all" mode).
</agent_identity>
<global_forbidden priority="maximum">
CRITICAL — FORBIDDEN at ALL times:
- Generating a plan without first reading
.ame/spec.md - Starting Chunk N+1 without explicit user confirmation — unless the user said "run all" before execution started (see Step 5)
- Hardcoding chunk count — chunk count is ALWAYS derived from layer analysis
- Skipping the risk section at the top of the plan
- Beginning execution without presenting the plan summary to the user first
- Writing files outside the explicit file list of the current chunk
- Treating Layer 2 as always-present — it is absent for headless, CLI, embedded (no comms layer), and pure-backend projects
- Running the validation gate of Chunk N after starting Chunk N+1
Triple Lock:
- STATE: Read spec → derive layers → determine chunks → generate plan → present → execute (confirmed)
- FORBID: FORBIDDEN: Skipping steps, hardcoding chunks, executing without user seeing the plan summary first
- REQUIRE: REQUIRED: Every chunk has a validation gate. Every LOW-confidence spec section is a plan risk.
Violation invalidates the plan. Restart /ema if violated.
</global_forbidden>
<tool_control priority="high">
REQUIRED tools (Agent mode only):
- File read: to read
.ame/spec.md- Aliases:
read_file/Read/localGetFileContent
- Aliases:
- File write / create / edit: to write
.ame/plan.mdand execute chunks- Aliases:
create_file/Write/StrReplace/edit_file/replace_string_in_file
- Aliases:
FORBIDDEN tools during planning phase (Steps 1–4):
- Any terminal execution, test runners, or linters — these run only inside chunk validation gates
Mode requirement:
/emaREQUIRES agent/agentic mode with file-write capability (VS Code Agent mode, Google Antigravity, or Claude Code)- IF file read/write tools are unavailable → STOP, output: "⚠️ /ema requires agent mode to read
.ame/spec.mdand write files. If you are in VS Code, switch to Agent mode. In Antigravity or Claude Code, ensure you are in the agent/agentic pane. Then re-invoke /ema."
</tool_control>
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.
- 2mo ago First seen · 378 lines · 117 tokens per session scan A e635d5b8141b
ema is a skill published in the GitHub repository CSKishan/ame-skill (5 stars, last pushed 6mo ago), licensed MIT. It adds 117 tokens to every session and 3,616 once invoked, about $0.0005 per session on Opus 5.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 skills, from other repositories
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
skill-doc-delivery
Convert markdown to DOCX, PPTX, XLSX, PDF office documents — use when you need exportable deliverables.
skill-writing-plans
Create zero-context implementation plans with bite-sized tasks — use for multi-step feature planning.
go-testing
Trigger: Go tests, go test coverage, Bubbletea teatest, golden files. Apply focused Go testing patterns.
bf-to-agents-sdk-dotnet-migration
Use when migrating a Bot Framework .NET SDK bot to Microsoft 365 Agents SDK. Triggered by projects that depend on packages: Microsoft.Bot.Builder or Microsoft.Bot.Builder.Integration.AspNet.Core that want to migrate to Agents SDK.
threejs-textures
Three.js textures - texture types, UV mapping, environment maps, texture settings. Use when working with images, UV coordinates, cubemaps, HDR environments, or texture optimization.