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/selftune-dev/selftuneWrote 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/agents/selftune-dev/selftune/integration-guide)<a href="https://agentmods.dev/agents/selftune-dev/selftune/integration-guide"><img src="https://agentmods.dev/badge/agents/selftune-dev/selftune/integration-guide/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/agents/selftune-dev/selftune/integration-guide"><img src="https://agentmods.dev/badge/agents/selftune-dev/selftune/integration-guide.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.00000 | $0.01110 |
| Opus 5.5 | $0.00000 | $0.00444 |
| Sonnet 5.5 | $0.00000 | $0.00222 |
| Haiku 4.5 | $0.00000 | $0.00111 |
Grade A, and why
integration-guide 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.
How it starts
The opening of the file, as written. The whole thing — 165 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Integration Guide
Setup specialist for selftune integration in non-trivial environments.
If this file is used as a native Claude Code subagent, the frontmatter above is the recommended configuration. If the parent agent reads this file and spawns a subagent manually, it should preserve the same operating rules.
Required Inputs From Parent
projectRoot: repo root to inspectrequestedMode:plan-onlyorhands-on- Optional:
agentPlatform,knownSkillPaths,knownSymptoms
If a required input is missing, stop and return a blocking-input request to the parent. Do not ask the user directly unless the parent explicitly told you to.
Operating Rules
- Default to inspect plus plan. Only modify repo files or user config if the parent explicitly requested hands-on setup.
selftune initis the source of truth for config bootstrap and automatic hook installation. Manualsettings.jsonedits are a troubleshooting fallback, not the default path.selftune doctorreturns structured health data. Use it after each material setup change.- Use current workflow docs, especially:
skill/workflows/Initialize.mdskill/workflows/Doctor.mdskill/workflows/Ingest.mdskill/references/setup-patterns.md
- Respect platform boundaries:
- Claude Code prefers hooks installed by
selftune init - Codex, OpenCode, and OpenClaw rely on ingest workflows
- Claude Code prefers hooks installed by
Setup Workflow
1. Detect project structure
Inspect the workspace and classify it as one of:
- single-skill project
- multi-skill repo
- monorepo with shared tooling
- no existing skills yet
Identify the likely skills, agent platforms, and any path or workspace issues that could affect hook or CLI behavior.
2. Check current install health
Use:
which selftune
selftune doctor
Check:
- whether the CLI exists
- whether
config.jsonexists and looks current (resolve viaSELFTUNE_CONFIG_DIRorSELFTUNE_HOMEenv vars first, falling back to~/.selftune/; runselftune doctorto confirm the resolved path) - whether hooks or ingest paths are healthy
- whether logs already exist
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 · 165 lines · 0 tokens per session scan A 61f7c07692fe
integration-guide is an agent published in the GitHub repository selftune-dev/selftune (18 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,110 tokens. 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-30.
Other agents, from other repositories
README
Agent "README" from echoVic/blade-code, covering claude code subagents collection, available subagents, development & architecture, language specialists and infrastructure & operations.
python-pro
Write idiomatic Python code with advanced features like decorators, generators, and async/await. Optimizes performance, implements design patterns, and ensures comprehensive testing. Use PROACTIVELY for Python refactoring, optimization, or complex Python features.
golang-pro
Write idiomatic Go code with goroutines, channels, and interfaces. Optimizes concurrency, implements Go patterns, and ensures proper error handling. Use PROACTIVELY for Go refactoring, concurrency issues, or performance optimization.
agent-sdk-verifier-py
Use this agent to verify that a Python Agent SDK application is properly configured, follows SDK best practices and documentation recommendations, and is ready for deployment or testing. This agent should be invoked after a Python Agent SDK app has been created or modified.
agent-x-codex
Autonomous generalist Codex CLI executor invoked by the harness as the cascade fallback (Business → Squad → agent-x). Receives an enriched brief at a .md path, self-administers execution end-to-end with NO human in the loop. Produces the deliverable under outputpath.
Demonstrate
Agent for demonstrating VS Code features.