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 walterra/eddoapp --skill eddo-workgit clone --depth 1 https://github.com/walterra/eddoappWrote 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/walterra/eddoapp/eddo-work)<a href="https://agentmods.dev/skills/walterra/eddoapp/eddo-work"><img src="https://agentmods.dev/badge/skills/walterra/eddoapp/eddo-work/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/walterra/eddoapp/eddo-work"><img src="https://agentmods.dev/badge/skills/walterra/eddoapp/eddo-work.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 54 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00068 | $0.02715 |
| Opus 5.5 | $0.00027 | $0.01086 |
| Sonnet 5.5 | $0.00014 | $0.00543 |
| Haiku 4.5 | $0.00007 | $0.00271 |
Grade A, and why
eddo-work 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 1mo 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 — 382 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Eddo Work
Structured implementation phases for complex tasks. Uses eddo-todo for task management.
Related Skills
- eddo-todo: Core task management commands (REQUIRED - load this skill first)
Prerequisites
Load the eddo-todo skill first and set up variables:
# Inside Docker container:
EDDO="${PI_CODING_AGENT_DIR:-/home/agent/.pi/agent}/skills/eddo-todo/eddo-todo.js"
BRANCH=$(git branch --show-current 2>/dev/null || echo "none")
METADATA='{"agent:session":"YOUR_PI_SESSION_ID","agent:model":"YOUR_PI_MODEL","agent:cwd":"YOUR_PI_CWD","agent:branch":"'$BRANCH'"}'
File Tracking
Track all files you modify during implementation in the agent:files metadata field (array of relative paths). This enables the Eddo UI to show which files were touched per task.
Update metadata when you modify files:
# After modifying files, update the parent todo's metadata
$EDDO update $PARENT_ID -M '{"agent:session":"...","agent:files":["src/Button.tsx","src/utils.ts"]}' -m "Updated file list"
Get current file list from git:
# Files changed in current branch vs main
git diff --name-only main...HEAD
Trigger Pattern
User: "what next?"
Agent: Suggests task from `$EDDO next`
User: "let's work on this" / "start working"
Agent: Enters work mode with structured phases
Critical Rules
- Test every change - never assume fixes work without verification
- Only complete subtasks when FULLY WORKING and VERIFIED
- Never git commit/push without user confirmation
- Follow all workflow phases - no shortcuts
- STOP at gates for user check-in
- MANDATORY: Execute reflection checklist at end of EVERY phase
- MANDATORY: Output reflection results with ✅/❌ for each item
Phase 1: REFINE
Start session:
$EDDO start <id> -M "$METADATA" -m "Starting REFINE phase"
$EDDO get <id>
Investigate:
- Review todo description for context and requirements
- Read relevant codebase files
- Ask clarifying questions if needed
- Define success criteria
- Log surprising findings:
$EDDO note <id> "Discovered X depends on deprecated Y"
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.
- 1mo ago First seen · 382 lines · 68 tokens per session scan A 4b56899c0b11
eddo-work is a skill published in the GitHub repository walterra/eddoapp (58 stars, last pushed today), licensed Apache-2.0. It adds 68 tokens to every session and 2,715 once invoked, about $0.0003 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-30.
Other skills, from other repositories
pace-bridge
Use to bridge a confirmed Superpowers/native plan into PACEflow CHG/HOTFIX artifacts, create artifact-writer prompts, and mark the specific plan as synced.
omc-plan
Strategic planning with optional interview workflow.
project-session-manager
Worktree-first dev environment manager for issues, PRs, and features with optional tmux sessions.
ultragoal
Durable multi-goal workflow that persists plan/ledger artifacts under .omc/ultragoal and prints Claude /goal handoff text for the active session.
google-tasks-tool
Google Tasks integration tool. Performs task list and task listing, addition, and updates using OAuth2. Use when: Use when: you need to fetch the TODO list, add tasks, update completion, or switch task lists.
speckit-workflow
Comprehensive understanding of the spec-kit methodology. Constitution-driven feature development with specify, plan, tasks, and implement phases.