006-documentation

A set of thin AI-tool wrappers that run the limps command-line interface, where MCP is a standard way for AI systems to call external tools.

In plain words
What is it for?
Use it to expose graph health checks, search, and related CLI commands to AI tools while keeping the command-line interface as the source of truth.
Why use it?
It lets tools that cannot run shell commands access the same graph operations without duplicating the underlying logic.

Agent

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/paulbreuler/limps/006-documentation
Clone the repo
git clone --depth 1 https://github.com/paulbreuler/limps
Per session 0 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,625 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. 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.00000 $0.01625
Opus 5 $0.00000 $0.00813
Sonnet 5 $0.00000 $0.00325
Haiku 4.5 $0.00000 $0.00162

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

Security

Grade A, and why

006-documentation scanned grade A with 1 finding 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.

Runs shell commandslowCapability

Expected in a hook, worth knowing in a rule or an instructions file.

import { exec } from 'child_process';
plans/0042-Knowledge Graph Foundation/agents/006-documentation.agent.md · 248 lines

How it starts

The opening of the file, as written. The whole thing — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Agent 006: MCP Wrappers

Objective

Create thin MCP wrappers around CLI commands. MCP tools are just exec('limps ...').

Context

MCP exists for tools that can't shell out.
If you're in a terminal, use CLI directly.
MCP is overhead when `limps graph health` does the same thing.

The MCP tools should be thin wrappers with no business logic. All intelligence lives in CLI.

Tasks

1. Tool Definitions (src/mcp/tools/graph.ts)

import { z } from 'zod';
import { exec } from 'child_process';
import { promisify } from 'util';

const execAsync = promisify(exec);

export const graphTools = {
  
  graph_health: {
    name: 'graph_health',
    description: 'Run health check on knowledge graph. Detects file contention, feature overlap, circular dependencies, stale WIP.',
    inputSchema: z.object({}),
    handler: async () => {
      const { stdout } = await execAsync('limps graph health --json');
      return JSON.parse(stdout);
    },
  },
  
  graph_search: {
    name: 'graph_search',
    description: 'Hybrid search across knowledge graph. Deterministically routes to lexical/semantic/graph retrieval.',
    inputSchema: z.object({
      query: z.string().describe('Search query'),
      top: z.number().optional().default(10).describe('Number of results'),
    }),
    handler: async ({ query, top }) => {
      const { stdout } = await execAsync(`limps graph search "${query}" --top ${top} --json`);
      return JSON.parse(stdout);
    },
  },
  
  graph_trace: {
    name: 'graph_trace',
    description: 'Trace dependencies from an entity (plan, agent, file).',
    inputSchema: z.object({
      entity: z.string().describe('Entity canonical ID (e.g., agent:0042#003)'),
      direction: z.enum(['up', 'down', 'both']).optional().default('both'),
      depth: z.number().optional().default(3),
    }),
    handler: async ({ entity, direction, depth }) => {
      const { stdout } = await execAsync(`limps graph trace "${entity}" --direction ${direction} --depth ${depth} --json`);
      return JSON.parse(stdout);
    },
  },
  
  graph_entity: {
    name: 'graph_entity',
    description: 'Get details about a specific entity and its relationships.',
    inputSchema: z.object({
      id: z.string().describe('Entity canonical ID'),
    }),
    handler: async ({ id }) => {
      const { stdout } = await execAsync(`limps graph entity "${id}" --json`);
      return JSON.parse(stdout);
    },
  },
  
  graph_overlap: {
    name: 'graph_overlap',
    description: 'Find similar/duplicate features across plans.',
    inputSchema: z.object({
      plan: z.string().optional().describe('Filter to specific plan'),
      threshold: z.number().optional().default(0.8).describe('Similarity threshold (0-1)'),
    }),
    handler: async ({ plan, threshold }) => {
      let cmd = `limps graph overlap --threshold ${threshold} --json`;
      if (plan) cmd += ` --plan ${plan}`;
      const { stdout } = await execAsync(cmd);
      return JSON.parse(stdout);
    },
  },
  
  graph_reindex: {
    name: 'graph_reindex',
    description: 'Reindex knowledge graph from plan files.',
    inputSchema: z.object({
      plan: z.string().optional().describe('Reindex specific plan only'),
      incremental: z.boolean().optional().default(false).describe('Only reindex changed files'),
    }),
    handler: async ({ plan, incremental }) => {
      let cmd = 'limps graph reindex --json';
      if (plan) cmd += ` --plan ${plan}`;
      if (incremental) cmd += ' --incremental';
      const { stdout } = await execAsync(cmd);
      return JSON.parse(stdout);
    },
  },
  
  graph_check: {
    name: 'graph_check',
    description: 'Run specific conflict check (contention, overlap, dependencies, stale).',
    inputSchema: z.object({
      type: z.enum(['contention', 'overlap', 'dependencies', 'stale']),
    }),
    handler: async ({ type }) => {
      const { stdout } = await execAsync(`limps graph check ${type} --json`);
      return JSON.parse(stdout);
    },
  },
  
  graph_suggest: {
    name: 'graph_suggest',
    description: 'Get suggestions (consolidate plans, next task).',
    inputSchema: z.object({
      type: z.enum(['consolidate', 'next-task']),
      plan: z.string().optional().describe('Plan ID for next-task'),
    }),
    handler: async ({ type, plan }) => {
      let cmd = `limps graph suggest ${type} --json`;
      if (plan) cmd += ` --plan ${plan}`;
      const { stdout } = await execAsync(cmd);
      return JSON.parse(stdout);
    },
  },
};

Read the full file on GitHub · 248 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 · 248 lines · 0 tokens per session scan A 674c2596e7b9

Subscribe to this mod's changes

006-documentation is an agent published in the GitHub repository paulbreuler/limps (10 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,625 tokens. A static security scan graded it A with 1 finding (runs shell commands). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.