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 instructions/forketyfork/walkthrough-plugin/claude-mdgit clone --depth 1 https://github.com/forketyfork/walkthrough-pluginWhat 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.01625 | $0.01625 |
| Opus 5 | $0.00813 | $0.00813 |
| Sonnet 5 | $0.00325 | $0.00325 |
| Haiku 4.5 | $0.00162 | $0.00162 |
Grade A, and why
walkthrough-plugin CLAUDE.md 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.
How it starts
The opening of the file, as written. The whole thing — 145 lines — stays where its author put it; the contents beside it link to each section on GitHub.
CLAUDE.md (symlinked as AGENTS.md)
[Canonical file: CLAUDE.md. Keep AGENTS.md as a symlink to CLAUDE.md.]
Project
Name: Walkthrough Plugin Description: IntelliJ IDEA plugin for presenting inline walkthrough guidance inside the editor. Shows styled popups near target lines with a connector anchored to the line, and lets the user step through a sequence of walkthrough items. Built with JetBrains Compose via the Jewel library. Stack: Kotlin 2.3.21, JetBrains Compose (Jewel), IntelliJ Platform Gradle Plugin v2, Detekt Status: Active development
Build & Run
# Environment bootstrap
# Prerequisites: Nix (https://nixos.org/download), direnv (https://direnv.net)
direnv allow # or: nix develop
# Build
just build # or: ./gradlew buildPlugin
# Run in a sandboxed IDE instance
just run # or: ./gradlew runIde
# Verify plugin compatibility
just verify # or: ./gradlew verifyPlugin
# Lint (everything CI runs: nix flake check + Detekt)
just lint # or: nix flake check && ./gradlew detekt
# Run unit tests
just test # or: ./gradlew test
# Clean
just clean # or: ./gradlew clean
# Publish to JetBrains Marketplace
just publish # or: ./gradlew publishPlugin
# Install pre-commit hooks (inside the Nix dev shell)
just hooks
The plugin is also tested by running it in the IDE via runIde.
Infrastructure
- Source code hosting: GitHub — URL:
https://github.com/forketyfork/walkthrough-plugin— Skill:managing-github - Issue tracker: GitHub Issues — URL:
https://github.com/forketyfork/walkthrough-plugin/issues— Skill:managing-github - CI/CD: GitHub Actions — configs:
.github/workflows/build.yml,.github/workflows/release.yml - Issue/PR linkage convention: Reference issues in PR descriptions using
Closes #<number>orFixes #<number>to auto-close on merge. Include the issue number in the PR title as(#<number>).
Architecture
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 · 145 lines · 1,625 tokens per session scan A 8bd18b6be6e1
walkthrough-plugin CLAUDE.md is an instructions file published in the GitHub repository forketyfork/walkthrough-plugin (10 stars, last pushed 5d ago), licensed MIT. It adds 1,625 tokens to every session, about $0.0081 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 instructions, from other repositories
Amarok-Hider AGENTS.md
Instructions for deltazefiro/Amarok-Hider, covering amarok, project overview, build, e2e test and agent rules.
AppClaw CLAUDE.md
Instructions for appclawhq/AppClaw, covering claude.md, what is appclaw?, build & run commands, architecture and entry point & cli modes (src/index.ts).
MobiAI-Core CLAUDE.md
Instructions for ArisGuimera/MobiAI-Core, covering mobiai — mobile development ai ecosystem, bootstrap and principles.
freetube CLAUDE.md
Instructions for leshkodev/freetube, covering claude.md, 1. what this project is, 2. non-negotiable constraints, 3. tech stack (locked) and 4. project structure.
ConsultMe CLAUDE.md
Instructions for Tarek-Bohdima/ConsultMe, covering claude.md, project context, common commands, module graph and conventions enforced by tooling.
Plonk AGENTS.md
Instructions for ostapondo/Plonk, covering agent rules, layout, adding a module, build & verify and code style.