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 skills/junghwayang/oh-my-codex/econpx skills add junghwaYang/oh-my-codex --skill ecogit clone --depth 1 https://github.com/junghwaYang/oh-my-codexWrote 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/junghwayang/oh-my-codex/eco)<a href="https://agentmods.dev/skills/junghwayang/oh-my-codex/eco"><img src="https://agentmods.dev/badge/skills/junghwayang/oh-my-codex/eco.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.00000 | $0.00363 |
| Opus 5 | $0.00000 | $0.00181 |
| Sonnet 5 | $0.00000 | $0.00073 |
| Haiku 4.5 | $0.00000 | $0.00036 |
Grade A, and why
eco 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.
What it actually says
Eco Skill
Token-efficient mode for simple tasks.
When to Use
- Simple, well-understood tasks
- Quick fixes and small changes
- When user values speed over explanation
- Routine operations
When NOT to Use
- Complex architectural decisions
- When user needs to understand the changes
- Debugging (need verbose output)
- Learning/teaching scenarios
Principles
1. MINIMAL CONFIRMATION
- Don't ask "shall I proceed?" for obvious tasks
- Just do it, show the result
2. TERSE OUTPUT
- Skip explanations unless asked
- Show diff, not description
- One-line summaries
3. FAST ROUTING
- Use simplest approach
- Avoid over-engineering
- Skip optional validations for trivial changes
4. BATCH WHEN POSSIBLE
- Combine related small changes
- Single commit for related fixes
Response Format
✓ {what was done}
That's it. No preamble, no follow-up questions unless truly needed.
Examples
User: "eco: add .env to gitignore" Response:
✓ Added .env to .gitignore
User: "eco: fix the typo in line 42" Response:
✓ Fixed "recieve" → "receive" in src/utils.ts:42
Anti-patterns
❌ "I'll help you add .env to your .gitignore file. Let me first check if the file exists..."
❌ "Done! I've successfully added .env to your .gitignore. Is there anything else you'd like me to help with?"
✅ "✓ Added .env to .gitignore"
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 · 68 lines · 0 tokens per session scan A 20a9c2ab1824
eco is a skill published in the GitHub repository junghwaYang/oh-my-codex (5 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 363 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
imagegen
Generate or edit raster images when the task benefits from AI-created bitmap visuals such as photos, illustrations, textures, sprites, mockups, or transparent-background cutouts. Use when Codex should create a brand-new image, transform an existing image, or derive visual variants from references, and the output…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…