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/bidiche49/claude-conf/startnpx skills add Bidiche49/claude-conf --skill startgit clone --depth 1 https://github.com/Bidiche49/claude-confWrote 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/bidiche49/claude-conf/start)<a href="https://agentmods.dev/skills/bidiche49/claude-conf/start"><img src="https://agentmods.dev/badge/skills/bidiche49/claude-conf/start.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.00014 | $0.00299 |
| Opus 5 | $0.00007 | $0.00150 |
| Sonnet 5 | $0.00003 | $0.00060 |
| Haiku 4.5 | $0.00001 | $0.00030 |
Grade A, and why
start 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 4d 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
Load the current session context and display a brief summary. Follow these steps:
- Run
git statusandgit log --oneline -10 - Scan
BACKLOG/— count pending and done tickets by type (bugs, features, improvements) - Check if
.claude-sessions/HANDOFF-*.mdexists — if yes, mention the most recent one (date + subject, 1 line). NEVER load the handoff automatically — just mention it exists. - Read the project's
CLAUDE.md(not the global one)
Display a summary in this format:
SESSION — [project name] ([stack])
═══════════════════════════════
Git : branch [name], [N] ahead, [N] modified files
Backlog: [N] pending ([breakdown]) / [N] done
Handoff: [filename] ([subject])
→ To resume, just ask.
Ready. What are we working on?
Rules — NON-NEGOTIABLE
- NEVER load the handoff automatically — just mention it exists
- NEVER propose what to work on — wait for the user
- Summary MUST fit in 5-6 lines max
- If no BACKLOG/ exists, skip that line
- If no handoff exists, skip that line
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.
- 4d ago First seen · 32 lines · 14 tokens per session scan A 6a2ba4565cc2
start is a skill published in the GitHub repository Bidiche49/claude-conf (2 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 299 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 skills, from other repositories
doctor
OrchestKit doctor for health diagnostics across manifest integrity, hook configuration, skill validation, agent frontmatter, MCP server connectivity, CC version compatibility, and permission rules. Reports issues with severity levels and auto-remediation suggestions. Validates component counts, detects orphaned…
decision-ledger
Maintain an append-only decision ledger (DECISIONS.md). Use when the user confirms a decision, reverses or changes a past decision, asks what was decided and why, or at session start to load standing decisions.
knowledge-base
Keep verified findings in memory/knowledge/ so the same research is never done twice. Use before researching any topic, when a finding passes the verify gate, or when about to answer from something learned in an earlier session.
pin
Turn a correction or working preference the user just expressed into a permanent ballast rule. Use when the user corrects your behavior, says "don't do X" / "always do Y" / "I told you before", or asks you to remember how they want things done.
catchup
Restore context after /clear by summarizing recent work and project state.
brain-init
Scaffold a file-based memory system (index, decision ledger, open questions, session log, optional product truth file) so a project can serve as a durable second brain. Use when the user wants to set up memory, an external brain, or the ballast structure in a project.