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 completion-reportgit 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/completion-report)<a href="https://agentmods.dev/skills/karthick-ramachandran/persist-os/completion-report"><img src="https://agentmods.dev/badge/skills/karthick-ramachandran/persist-os/completion-report/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/completion-report"><img src="https://agentmods.dev/badge/skills/karthick-ramachandran/persist-os/completion-report.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.00046 | $0.00349 |
| Opus 5 | $0.00023 | $0.00175 |
| Sonnet 5 | $0.00009 | $0.00070 |
| Haiku 4.5 | $0.00005 | $0.00035 |
Grade A, and why
completion-report 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 10d 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
Skill: Completion Report
Purpose
Record evidence that a task is complete and safe to review.
Inputs
- Task or feature summary.
- Files changed.
- Commands run.
- Test results.
- Docs updated.
- Known risks.
Required Reading
docs/50-quality/QUALITY_GATES.mddocs/60-engineering/ENGINEERING_STANDARDS.md- Relevant feature
TASKS.md - Relevant feature
TEST_PLAN.md - Relevant feature
REVIEW.md
Output Files
- Relevant feature
COMPLETION_REPORT.md - Task or feature docs that need final status updates.
Process
- Summarize the completed scope.
- List files changed by category.
- List commands run and results.
- List skipped checks and why.
- List docs updated.
- State whether engineering standards were followed.
- List remaining risks and follow-up work.
- State whether the task meets the definition of done.
Stop Conditions
Stop and request human decision if:
- Test results are missing for risky changes.
- Completion claims conflict with evidence.
- Required docs were not updated.
- Engineering standards were violated.
- Remaining risks are release blockers.
Quality Bar
- The report is evidence-based.
- It does not hide skipped checks.
- It separates completed work from remaining risk.
- A reviewer can decide what to do next from the report alone.
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.
- 10d ago First seen · 64 lines · 46 tokens per session scan A 793ea41a522e
completion-report is a skill published in the GitHub repository Karthick-Ramachandran/persist-os (8 stars, last pushed 2mo ago), licensed MIT. It adds 46 tokens to every session and 349 once invoked, about $0.0002 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
dream
Batch-execute SHIP-ready wishes overnight — pick wishes, orchestrate workers, review PRs, wake up to results.
clickup
Use when managing ClickUp tasks, sprints, or comments via the cup CLI tool. Triggers: task queries, status updates, sprint tracking, creating subtasks, posting comments, threaded replies, standup summaries, searching tasks, checking overdue items, assigning tasks, listing spaces and lists, opening tasks in browser…
sw-do
Implement a SpecWeave increment task by task through the ledger, with evidence per task and a verified close. Use for "implement this", "start working", "continue the increment", "keep going".
workspace
Multi-repo workspace coordinator for shared team context. Initialize .adlc/ structure, configure .gitignore, discover child repos, link them as Git submodules, and audit workspace health. Use --init for first-time setup, default mode for ongoing auditing.
done
Close an increment: ledger check, specweave verify, optional review, then specweave complete. Use when all tasks are done and saying "close increment", "we are done", or "finish up".
product-roadmap
Track milestone progress across four layers of truth — decision state (PDR status), execution state (live issue tracker via MCP), evidence state (code-vs-PDR verification), and gate state (milestone gates). Shows honest completion, done-means warnings, and updates status only when all layers are green. Use for weekly…