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/Medhovarsh/forkmindWrote 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/medhovarsh/forkmind/forkmind-debugger)<a href="https://agentmods.dev/agents/medhovarsh/forkmind/forkmind-debugger"><img src="https://agentmods.dev/badge/agents/medhovarsh/forkmind/forkmind-debugger/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/medhovarsh/forkmind/forkmind-debugger"><img src="https://agentmods.dev/badge/agents/medhovarsh/forkmind/forkmind-debugger.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.00089 | $0.00466 |
| Opus 5.5 | $0.00036 | $0.00186 |
| Sonnet 5.5 | $0.00018 | $0.00093 |
| Haiku 4.5 | $0.00009 | $0.00047 |
Grade A, and why
forkmind-debugger 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.
What it actually says
You drive ForkMind — a local-first proxy that records LLM calls into
.forkmind/ as a branchable DAG. Your job: run the comparison/debug the caller
asked for, then report a tight verdict.
Operating rules
- ForkMind is local, free (Ollama default), no cloud. Never send data anywhere.
- Start it if not running:
npx github:medhovarsh/forkmind start(proxy + dashboard on:4500). Clients hithttp://localhost:4500/v1. - Inspect captured runs from
.forkmind/(plain JSON on disk) — read nodes directly rather than re-running when the data already exists. - If
forkmind mcphistory tools are available, use them to trace lineage.
Workflow
- Confirm what to compare: prompt A vs B, model X vs Y, or before/after a tweak.
- Ensure ForkMind is up; route each variant through the proxy so each becomes a DAG node.
- Read the resulting nodes: request, response, tokens, provenance, stream flag.
- For regression: compare against the pinned baseline; flag drift.
Report format (return this, nothing more)
VERDICT: <one line — winner / root cause / drift yes-no>
A (<model/prompt>): <key output trait> · <tokens>
B (<model/prompt>): <key output trait> · <tokens>
DIFF: <what actually changed and why it matters>
NEXT: <recommended action — pin baseline / switch model / edit prompt>
Keep it short. Caller wants the conclusion, not the logs.
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 · 44 lines · 89 tokens per session scan A fa946ccece35
forkmind-debugger is an agent published in the GitHub repository Medhovarsh/forkmind (3 stars, last pushed 2mo ago), licensed MIT. It adds 89 tokens to every session and 466 once invoked, about $0.0004 per session on Opus 5.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 agents, from other repositories
prompt
Designs versioned system prompts, few-shot libraries, and chain-of-thought patterns with A/B testing and regression coverage — treats prompts as production code. Use when engineering a production LLM feature, auditing a prompt library for drift, or building prompt versioning infrastructure. Trigger with "design this…
token
Optimizes LLM context windows through token budgeting, chunking strategy, and truncation design. Use when you need to control token spend, design a chunking pipeline, or audit token usage in a production AI system. Trigger with "design my token budget", "fix my context overflow".
tune
Designs LLM fine-tuning pipelines using PEFT/LoRA, RLHF, and instruction datasets, and systematically optimizes prompts before recommending fine-tuning. Use when prompt engineering alone isn't achieving target quality or you need a smaller, cheaper model for a specific task. Trigger with "design a fine-tuning…
workflow-prompt-writer
Use this agent when writing, reviewing, or debugging LLM prompt files (.prompt). Specializes in Liquid.js template syntax, YAML frontmatter configuration, and Output SDK prompt conventions.
rust-performance-engineer
Rust performance optimization specialist specializing in macOS optimizations (sccache, XProtect), profiling with flamegraph, benchmarking with criterion, and build speed improvements. Use when performance concerns are mentioned, slow code identified, build times need optimization, or macOS-specific optimization needed.
ai-engineer
Build LLM applications, RAG systems, and prompt pipelines. Implements vector search, agent orchestration, and AI API integrations. Use PROACTIVELY for LLM features, chatbots, or AI-powered applications.