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/s3yed/appie-kit/plannpx skills add S3YED/appie-kit --skill plangit clone --depth 1 https://github.com/S3YED/appie-kitWrote 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/s3yed/appie-kit/plan)<a href="https://agentmods.dev/skills/s3yed/appie-kit/plan"><img src="https://agentmods.dev/badge/skills/s3yed/appie-kit/plan.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.00035 | $0.00457 |
| Opus 5 | $0.00017 | $0.00229 |
| Sonnet 5 | $0.00007 | $0.00091 |
| Haiku 4.5 | $0.00003 | $0.00046 |
Grade A, and why
plan 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 3d 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.
This is a copy
88% identical to plan — 5 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
What it actually says
Plan Mode
Use this skill when the user wants a plan instead of execution.
Core behavior
For this turn, you are planning only.
- Do not implement code.
- Do not edit project files except the plan markdown file.
- Do not run mutating terminal commands, commit, push, or perform external actions.
- You may inspect the repo or other context with read-only commands/tools when needed.
- Your deliverable is a markdown plan saved inside the active workspace under
.hermes/plans/.
Output requirements
Write a markdown plan that is concrete and actionable.
Include, when relevant:
- Goal
- Current context / assumptions
- Proposed approach
- Step-by-step plan
- Files likely to change
- Tests / validation
- Risks, tradeoffs, and open questions
If the task is code-related, include exact file paths, likely test targets, and verification steps.
Save location
Save the plan with write_file under:
.hermes/plans/YYYY-MM-DD_HHMMSS-<slug>.md
Treat that as relative to the active working directory / backend workspace. Hermes file tools are backend-aware, so using this relative path keeps the plan with the workspace on local, docker, ssh, modal, and daytona backends.
If the runtime provides a specific target path, use that exact path.
If not, create a sensible timestamped filename yourself under .hermes/plans/.
Interaction style
- If the request is clear enough, write the plan directly.
- If no explicit instruction accompanies
/plan, infer the task from the current conversation context. - If it is genuinely underspecified, ask a brief clarifying question instead of guessing.
- After saving the plan, reply briefly with what you planned and the saved path.
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.
- 3d ago First seen · 58 lines · 35 tokens per session scan A ecb0b3bf5eed
plan is a skill published in the GitHub repository S3YED/appie-kit (7 stars, last pushed 8d ago), licensed MIT. It adds 35 tokens to every session and 457 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 88% identical to plan, differing in 5 lines, and is treated as a copy.
Other skills, from other repositories
geo-pipeline
Entry point + orchestrator for the recomby-geo GEO (Generative Engine Optimization) workflow on OpenAI Codex CLI. Use when the user wants to run any stage of the GEO pipeline on a client folder — intake, visibility audit, content-gap analysis, content brief, draft production, distribution, or monthly re-audit — or…
schedule
Create, list, remove or inspect this bot's scheduled work — recurring jobs ("every morning at 7 tell me X", "every weekday at 9 post the standup") and one-shot follow-ups ("check back in 20 minutes", "watch that deploy until it lands", "remind me on Friday"). Use whenever something must happen on a schedule…
digest
Activate for: daily digest, morning briefing, what's happening today, start of day brief, week ahead, Monday brief, weekly digest, start of week, what do I need to know today, morning rundown, daily overview, what's due today, Friday close, end of week summary. NOT for: executive dashboard (use progress-tracker)…
meeting-intelligence
Activate for: meeting prep, meeting synthesis, before the meeting, after the meeting, D/A/F/Q/R, meeting brief, stakeholder prep, meeting notes synthesis, meeting follow-up, meeting actions, meeting decisions, post-meeting notes, synthesise the meeting, what was decided in the meeting, meeting record. NOT for…
task-intelligence
Activate for: brain dump, prioritise, P1 P2 P3, critical path, daily priorities, weekly planning, backlog review, cross-domain plan, what should I work on, capture everything in my head, sort my priorities, what is most important right now, weekly critical path. NOT for: basic task CRUD (use official productivity…
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.