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 commands/logicstamp/logicstamp-mcp/read-bundlegit clone --depth 1 https://github.com/LogicStamp/logicstamp-mcpWrote 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/commands/logicstamp/logicstamp-mcp/read-bundle)<a href="https://agentmods.dev/commands/logicstamp/logicstamp-mcp/read-bundle"><img src="https://agentmods.dev/badge/commands/logicstamp/logicstamp-mcp/read-bundle.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.03856 |
| Opus 5 | $0.00000 | $0.01928 |
| Sonnet 5 | $0.00000 | $0.00771 |
| Haiku 4.5 | $0.00000 | $0.00386 |
Grade A, and why
read-bundle 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 4d 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 — 499 lines — stays where its author put it; the contents beside it link to each section on GitHub.
logicstamp_read_bundle
STEP 3 of the LogicStamp MCP workflow. Call this to get the actual useful data - component contracts, dependencies, and style metadata.
Overview
logicstamp_read_bundle reads the full component bundle from a snapshot. This is where the actual useful data is. Call this after logicstamp_list_bundles to get detailed component information.
The command returns a complete UIFContract with:
- Props - Types, optional flags, descriptions
- State variables -
useStatehooks and their types - Hooks used - All React hooks in the component
- Dependency graph - What components/functions this imports
- Exports - Default and named exports
- Source code - Optional (based on
modefromrefresh_snapshot) - Style metadata - If
includeStyle: truewas used inrefresh_snapshot
Important: This is the ONLY way to see component contracts, dependencies, and style information. The refresh_snapshot summary does NOT include this data.
When to Use
- After listing bundles - Get detailed information about specific components
- Component analysis - Understand component props, state, and dependencies
- Dependency exploration - See what a component imports and uses
- Style analysis - Access style metadata when
includeStyle: truewas used - Code generation - Get component contracts for AI-assisted code generation
Parameters
snapshotId (required)
- Type:
string - Description: The snapshot ID returned from
logicstamp_refresh_snapshot. This identifies which snapshot to read from.
bundlePath (required)
-
Type:
string -
Description: Relative path to
context.jsonfile orcontext_main.json. Get this value from thebundlePathfield inlogicstamp_list_bundlesoutput.Examples:
"context_main.json"- Read the main index file (returns LogicStampIndex)"src/components/context.json"- Read a bundle file (returns LogicStampBundle)"src/pages/context.json"- Read a bundle file"src/utils/context.json"- Read a bundle file
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.
- 4d ago First seen · 499 lines · 0 tokens per session scan A e42adc74c18a
read-bundle is a command published in the GitHub repository LogicStamp/logicstamp-mcp (4 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 3,856 tokens. 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 commands, from other repositories
validate-dependencies
Validate all task dependencies for issues.
validate-prd
Validate an existing PRD against BMAD standards - comprehensive review for completeness, clarity, and quality.
editorial-review-structure
Structural editor that proposes cuts, reorganization, and simplification while preserving comprehension.
add-tool
Scaffold a new FreeAgent MCP tool (handler + registration + test) following the repo pattern.
codeweb-narrate
Write one-sentence, agent-authored summaries for each domain and the top load-bearing symbols into the .codeweb/narration.json sidecar — provenance-labeled, staleness-stamped, never touching graph.json.
OPSX: Archive
Archive a completed change in the experimental workflow.