walkthrough-plugin CLAUDE.md

Repository instructions for Walkthrough Plugin, an IntelliJ IDEA extension that displays guided, step-by-step help beside code lines. They cover the Kotlin project setup, building, running, testing and checks.

In plain words
What is it for?
Use them when developing, building, running or checking the Walkthrough Plugin. They also explain that AGENTS.md should remain a symlink to CLAUDE.md.
Why use it?
They give an agent the project rules and commands needed to work on the extension consistently, including how to prepare the environment and verify changes.

Instructions file

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 instructions/forketyfork/walkthrough-plugin/claude-md
Clone the repo
git clone --depth 1 https://github.com/forketyfork/walkthrough-plugin
Per session 1,625 This file is loaded in full into every session.
When invoked 1,625 The same file — it is already loaded in full.
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.

ModelPer sessionOnce 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

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

Security

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.

CLAUDE.md · 145 lines

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> or Fixes #<number> to auto-close on merge. Include the issue number in the PR title as (#<number>).

Architecture

Read the full file on GitHub · 145 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.

  1. 2d ago First seen · 145 lines · 1,625 tokens per session scan A 8bd18b6be6e1

Subscribe to this mod's changes

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.