Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add hoblin/claude-ruby-marketplace/plugin install rpiWrote 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/hoblin/claude-ruby-marketplace/thoughts_init)<a href="https://agentmods.dev/skills/hoblin/claude-ruby-marketplace/thoughts_init"><img src="https://agentmods.dev/badge/skills/hoblin/claude-ruby-marketplace/thoughts_init/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/hoblin/claude-ruby-marketplace/thoughts_init"><img src="https://agentmods.dev/badge/skills/hoblin/claude-ruby-marketplace/thoughts_init.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.00006 | $0.00558 |
| Opus 5.5 | $0.00002 | $0.00223 |
| Sonnet 5.5 | $0.00001 | $0.00112 |
| Haiku 4.5 | $0.00001 | $0.00056 |
Grade A, and why
thoughts_init 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.
What it actually says
Initialize Thoughts System
Initialize the thoughts system for the current repository.
Process
Step 1: Diagnostic Checks
Run these checks and collect results:
~/thoughtsexists:test -d "$HOME/thoughts"~/thoughtsis git repo:test -d "$HOME/thoughts/.git"~/thoughts/globalstructure exists:test -d "$HOME/thoughts/global"- Scripts exist:
test -x "$HOME/thoughts/bin/thoughts-sync" - Scripts in PATH:
command -v thoughts-sync >/dev/null 2>&1 - Current dir is git repo:
test -d ".git" ./thoughts/sharedsymlinked correctly:test -L "./thoughts/shared" && readlink "./thoughts/shared" | grep -q "thoughts/repos/"
Step 2: Report or Fix
If all checks pass:
Thoughts system ready. RPI workflow commands will now work correctly.
- ~/thoughts: OK (with global/ structure)
- Scripts: OK (in PATH)
- Repository: OK (thoughts/shared → ~/thoughts/repos/{repo}/shared)
If any check fails: Build todo list of what needs fixing, present to user, wait for authorization.
Step 3: Execute Fixes (after authorization)
If ~/thoughts missing:
mkdir -p "$HOME/thoughts/bin"
mkdir -p "$HOME/thoughts/global/$(whoami)"
mkdir -p "$HOME/thoughts/global/shared"
mkdir -p "$HOME/thoughts/repos"
git -C "$HOME/thoughts" init
cp "${CLAUDE_PLUGIN_ROOT}/templates/thoughts-bin/"* "$HOME/thoughts/bin/"
chmod +x "$HOME/thoughts/bin/"*
If PATH not configured:
RC_FILE="$HOME/.bashrc"
[[ "$SHELL" == *"zsh"* ]] && RC_FILE="$HOME/.zshrc"
echo 'export PATH="$HOME/thoughts/bin:$PATH"' >> "$RC_FILE"
Tell user to run source ~/.zshrc or restart terminal.
If current repo not initialized:
"$HOME/thoughts/bin/thoughts-init-repo"
Step 4: Verify and Report
After fixes, re-run checks and report final status.
Important
- Never make changes without user authorization
- If current directory is not a git repo, report error and stop
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 · 71 lines · 6 tokens per session scan A 35332cb9734f
thoughts_init is a skill published in the GitHub repository hoblin/claude-ruby-marketplace (37 stars, last pushed 1mo ago), licensed MIT. It adds 6 tokens to every session and 558 once invoked, about $0.0000 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-09-07.
Other skills, from other repositories
plan-orchestrator
Route hierarchical-planning intents to the correct backing script. Use when the user invokes /aura-frog:plan (with or without subcommand), mentions plan verbs (expand/next/replan/promote/archive/freeze/thaw/undo/status/conflicts), or types a plan-vocabulary bare word with .claude/plans/active.json present. Owns verb…
conflict-detector
L1-L4 conflict detection between a proposed T4 task and pending-confirm sibling tasks. L1 (file overlap) + L2 (function/region overlap) ship in v3.7.0-beta.2 as deterministic bash. L3 (semantic LLM) + L4 (architectural LLM) are stubbed for v3.7.0-rc.1.
plan-loader
Loads minimum hierarchical plan context (.claude/plans/) for current execution focus. Auto-invokes every session when plans exist. Stays under 800 always-loaded tokens regardless of plan tree size.
wrap-up
End-of-session handler: checks if the plan is complete. If complete: quick retrospective, forward follow-up prompt, and (in a repo) refresh + clean gone branches. If incomplete: skip cleanup, emit resume prompts. Cleanup needs a repo; rest doesn't.
track-followups
Record triaged follow-up work where it'll be seen: create the item in Vikunja or Zammad (incidents), deduplicating first and reporting the id. Use when session work outlives it or items were triaged elsewhere. Never opens a GitHub issue.
issue-sweep
Use when a tracker's open issues piled up, went stale, or stopped reflecting reality — maybe fixed, duplicated, vague, superseded — reconcile against actual code, group by root cause, turn into a plan. Any tracker. Use before a work session too.