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 Karthick-Ramachandran/persist-os --skill plan-modulegit clone --depth 1 https://github.com/Karthick-Ramachandran/persist-osWrote 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/karthick-ramachandran/persist-os/plan-module)<a href="https://agentmods.dev/skills/karthick-ramachandran/persist-os/plan-module"><img src="https://agentmods.dev/badge/skills/karthick-ramachandran/persist-os/plan-module/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/karthick-ramachandran/persist-os/plan-module"><img src="https://agentmods.dev/badge/skills/karthick-ramachandran/persist-os/plan-module.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.00050 | $0.00608 |
| Opus 5 | $0.00025 | $0.00304 |
| Sonnet 5 | $0.00010 | $0.00122 |
| Haiku 4.5 | $0.00005 | $0.00061 |
Grade A, and why
plan-module 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 9d 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 — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill: Plan Module
Purpose
Turn a module request into a complete delivery workflow before implementation starts.
Inputs
- Module name or request.
- Product goal or user need.
- Existing architecture, feature, or module docs.
- Known constraints or priority stage.
Required Reading
AGENTS.mddocs/00-product/PRD.mddocs/10-architecture/ARCHITECTURE.mddocs/20-security/SECURITY_MODEL.mddocs/50-quality/TESTING_STRATEGY.mddocs/60-engineering/ENGINEERING_STANDARDS.mddocs/ai/MODULE_DELIVERY_WORKFLOW.md- Relevant ADRs under
docs/adrs/
Output Files
docs/40-features/F-###-<module>-module/delivery docs (PRD, ACCEPTANCE, ARCHITECTURE_IMPACT, PLAN, TASKS, TEST_PLAN, REVIEW, COMPLETION_REPORT).docs/30-modules/<module>/MODULE.mddocs/30-modules/<module>/TASKS.mddocs/30-modules/<module>/TEST_PLAN.mddocs/30-modules/<module>/DECISIONS.md
Process
- Create a module brief: ownership, non-ownership, public interfaces, users, and use cases.
- Define behavior and edge cases.
- Write testable acceptance criteria.
- Document architecture impact, dependency impact, config impact, template impact, and ADR needs.
- Write the test plan from acceptance criteria, security invariants, and regression risk.
- Break work into ordered tasks with status, scope, acceptance, tests, and do-not-do boundaries.
- Mark implementation as blocked until the first task is selected.
Stop Conditions
Stop and request human decision if:
- The module ownership or public interface is unclear.
- The module conflicts with accepted ADRs or architecture docs.
- The module conflicts with engineering standards.
- The module requires runtime network, telemetry, cloud, MCP, AI API, auth, secrets, storage, or file write behavior changes without ADR or security review.
- The user asks to implement before PRD, acceptance, architecture impact, test plan, and tasks exist.
Quality Bar
- The module is planned as a mini product, not a file list.
- PRD, acceptance, architecture impact, test plan, and tasks are all present.
- Tasks are small enough to execute one at a time.
- Module memory captures what future agents need to remember.
- No implementation code is written by this skill.
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.
- 9d ago First seen · 71 lines · 50 tokens per session scan A d3c8c562cf2e
plan-module is a skill published in the GitHub repository Karthick-Ramachandran/persist-os (8 stars, last pushed 2mo ago), licensed MIT. It adds 50 tokens to every session and 608 once invoked, about $0.0003 per session on Opus 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
actual
Feature-complete companion for the actual CLI, an ADR-powered CLAUDE.md/AGENTS.md generator. Runs and troubleshoots actual adr-bot, status, auth, config, runners, and models, plus the Actual AI platform surface: login, logout, whoami, and advisor (org-scoped architecture Q&A). Covers all 5 runners (claude-cli…
architecture-governance
Keep code changes conformant to a repo's real, declared architecture using ArchSteer. Use when starting work in an unfamiliar repo, before finishing/committing an architecturally significant change (new dependency, new data access, new external call, new layer), or when asked about a codebase's architecture, layers…
rework-rate
Measure and interpret PR rework rate — the emerging 5th DORA metric.
work
Execute an approved wish plan — orchestrate subagents per task group with fix loops, validation, and review handoff.
openlore-brainstorm
Transform a feature idea into an annotated story using a Domain Sketch or Constrained Option Tree. Use when asked to brainstorm, explore, or shape a feature before implementation.
trace
Dispatch trace subagent to investigate unknown issues — reproduces, traces, and reports root cause for fix handoff.