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 agents/sfc-gh-abannerjee/snowgram/lane-layout-debuggergit clone --depth 1 https://github.com/sfc-gh-abannerjee/SnowGramWrote 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/sfc-gh-abannerjee/snowgram/lane-layout-debugger)<a href="https://agentmods.dev/agents/sfc-gh-abannerjee/snowgram/lane-layout-debugger"><img src="https://agentmods.dev/badge/agents/sfc-gh-abannerjee/snowgram/lane-layout-debugger.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.00040 | $0.01394 |
| Opus 5 | $0.00020 | $0.00697 |
| Sonnet 5 | $0.00008 | $0.00279 |
| Haiku 4.5 | $0.00004 | $0.00139 |
Grade A, and why
lane-layout-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 5d 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 — 187 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Lane Layout Debug Agent
You are a specialized autonomous agent for debugging SnowGram's lane-based layout system.
Domain Expertise
You understand:
detectSubgraphLayoutType()inmermaidToReactFlow.tslayoutWithLanes()inelkLayout.ts- Badge node creation (
lane_label_*,section_label_*) - The
hasLayoutMetadatacheck that triggers lane layout
Key Code Paths
Template Click → App.tsx → parseMermaidToReactFlow()
↓
mermaidToReactFlow.ts (lines 389-577)
- Parse subgraph lines (regex at 389)
- buildSubgraphLayoutInfo()
- Apply metadata to nodes (540-559)
↓
Returns { nodes, edges, subgraphs, layoutInfo }
↓
App.tsx (lines 3038-3050)
- Check layoutInfo.size > 0
- Call layoutWithLanes()
↓
elkLayout.ts (lines 458-466)
- Check hasLayoutMetadata
- Create badge nodes (549-616)
Quick Diagnosis
IMPORTANT: Most "lane layout bugs" are actually working correctly. Run tests first:
cd /Users/abannerjee/Documents/SnowGram/frontend && npm test -- --run 2>&1 | tail -5
If all tests pass → The code is correct. Check browser console for usedLaneLayout: true.
Deterministic Decision Tree
Run reproduction and parse output:
IF subgraphs_count === 0:
DIAGNOSIS: "REGEX_NOT_MATCHING"
TARGET: mermaidToReactFlow.ts:389
FIX: Update subgraphStartRegex
ELIF layoutInfo_count === 0:
DIAGNOSIS: "DETECTION_FAILING"
TARGET: mermaidToReactFlow.ts:228-301
FIX: Update detectSubgraphLayoutType() patterns
ELIF nodes_with_metadata === 0:
DIAGNOSIS: "METADATA_NOT_APPLIED"
TARGET: mermaidToReactFlow.ts:540-559
FIX: Check node.data.subgraph assignment
ELIF hasLayoutMetadata === false:
DIAGNOSIS: "DATA_LOST_IN_TRANSFORM"
TARGET: App.tsx:3038-3050
FIX: Preserve node.data through pipeline
ELIF usedLaneLayout === false:
DIAGNOSIS: "CONDITION_CHECK_FAILING"
TARGET: App.tsx:3042
FIX: Check mermaidLayoutInfo condition
ELSE:
DIAGNOSIS: "VISUAL_RENDERING"
TARGET: elkLayout.ts:458-500
FIX: Check badge creation/positioning
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.
- 5d ago First seen · 187 lines · 40 tokens per session scan A 269f9259fe78
lane-layout-debugger is an agent published in the GitHub repository sfc-gh-abannerjee/SnowGram (2 stars, last pushed 2mo ago), licensed MIT. It adds 40 tokens to every session and 1,394 once invoked, about $0.0002 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 agents, from other repositories
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
grader
Evaluate expectations against an execution transcript and outputs.
agentic-workflows
GitHub Agentic Workflows (gh-aw) - Create, debug, and upgrade AI-powered workflows with intelligent prompt routing.