What is integration-guide?

A setup specialist for selftune in complex repositories, including monorepos, mixed agent platforms, and workspaces with several skills. A monorepo is one repository containing multiple projects or packages.

Use it to inspect the project, validate selftune settings, create a setup plan, apply an explicitly requested setup, and run health checks after changes.

It helps resolve configuration and hook problems that basic setup and health checks do not explain.

integration-guide — Agent by selftune-dev

Install

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.

agentmods

npx agentmods add agents/selftune-dev/selftune/integration-guide

Clone the repo

git clone --depth 1 https://github.com/selftune-dev/selftune

Per session 61 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,110 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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.00061	$0.01110
Opus 5	$0.00030	$0.00555
Sonnet 5	$0.00012	$0.00222
Haiku 4.5	$0.00006	$0.00111

Measured 2d ago against content hash 61f7c07692fe, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

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 2d 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.

skill/agents/integration-guide.md · 165 lines

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 inspect
requestedMode: plan-only or hands-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 init is the source of truth for config bootstrap and automatic hook installation. Manual settings.json edits are a troubleshooting fallback, not the default path.
selftune doctor returns structured health data. Use it after each material setup change.
Use current workflow docs, especially:
- skill/workflows/Initialize.md
- skill/workflows/Doctor.md
- skill/workflows/Ingest.md
- skill/references/setup-patterns.md
Respect platform boundaries:
- Claude Code prefers hooks installed by selftune init
- Codex, OpenCode, and OpenClaw rely on ingest workflows

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.json exists and looks current (resolve via SELFTUNE_CONFIG_DIR or SELFTUNE_HOME env vars first, falling back to ~/.selftune/; run selftune doctor to confirm the resolved path)
whether hooks or ingest paths are healthy
whether logs already exist

Read the full file on GitHub · 165 lines

Changes

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.

2d ago First seen · 165 lines · 0 tokens per session scan A 61f7c07692fe

Subscribe to this mod's changes

integration-guide is an agent published in the GitHub repository selftune-dev/selftune (16 stars, last pushed 2d ago), licensed MIT. It adds 61 tokens to every session and 1,110 once invoked, about $0.0003 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-30.

Planning Productivity agent ai automation bun claude-code cli

integration-guide

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Integration Guide

Required Inputs From Parent

Operating Rules

Setup Workflow

1. Detect project structure

2. Check current install health

What this file has done since we first saw it

Other agents, from other repositories

observer

orchestrator

grok-bot

architect

author

executor