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.
git clone --depth 1 https://github.com/saisurya96/inner-child-healingWrote 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/commands/saisurya96/inner-child-healing/journal)<a href="https://agentmods.dev/commands/saisurya96/inner-child-healing/journal"><img src="https://agentmods.dev/badge/commands/saisurya96/inner-child-healing/journal/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/commands/saisurya96/inner-child-healing/journal"><img src="https://agentmods.dev/badge/commands/saisurya96/inner-child-healing/journal.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.00023 | $0.00363 |
| Opus 5 | $0.00012 | $0.00181 |
| Sonnet 5 | $0.00005 | $0.00073 |
| Haiku 4.5 | $0.00002 | $0.00036 |
Grade A, and why
journal 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.
What it actually says
View Journal
The user wants to look at their healing journey.
Read the Journal
Read ${CLAUDE_PLUGIN_DATA}/journal.json. If it doesn't exist or is empty, let the user know gently — they haven't had any sessions captured yet.
How to Present
Based on what the user asks (or the argument they pass):
/healing:journal recent (or no argument — this is the default)
Show the last 3-5 journal entries in a warm, readable format. Not raw JSON. Translate the structured notes into natural language — like a therapist reading back their notes in a way that feels personal, not clinical.
For each entry, convey:
- When it was (date, relative like "last Tuesday" when possible)
- What was explored
- What shifted, if anything
- Where things were left
/healing:journal all
Show the full journal chronologically, but still in readable narrative form. Group by time period if there are many entries.
/healing:journal summary
Synthesize the entire journey into a narrative arc:
- Where they started (initial wounds, initial state)
- What's been explored
- What shifts have happened (highlight the subtle ones — those matter most)
- Where things are now
- What threads are still open
Tone
This is someone looking back at their own healing. Treat it with care. Don't be clinical. Don't be overly dramatic. Just be honest and warm. Let them see how far they've come — or acknowledge that they're still in the thick of it. Both are valid.
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 · 42 lines · 23 tokens per session scan A 3620d6724462
journal is a command published in the GitHub repository saisurya96/inner-child-healing (2 stars, last pushed 5mo ago), licensed MIT. It adds 23 tokens to every session and 363 once invoked, about $0.0001 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 commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.