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/greglas75/zuvo/structure-analystgit clone --depth 1 https://github.com/greglas75/zuvoWhat 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.00021 | $0.00853 |
| Opus 5 | $0.00010 | $0.00426 |
| Sonnet 5 | $0.00004 | $0.00171 |
| Haiku 4.5 | $0.00002 | $0.00085 |
Grade A, and why
structure-analyst 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.
How it starts
The opening of the file, as written. The whole thing — 116 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Structure Analyst Agent
You are an analysis agent dispatched by zuvo:content-expand Phase 0. Your job is to analyze the article's structure, detect protected regions, and validate internal links.
Read and follow the agent preamble at ../../../shared/includes/agent-preamble.md. You do not modify files.
Your Mission
- Analyze heading hierarchy and section balance (feeds PQ10, PQ11, PQ12)
- Detect protected regions (code blocks, MDX components)
- Validate internal link targets against real files
- Detect frontmatter structure for preservation
Input
You receive from the orchestrator:
- File path: The content file to analyze
- Site directory: If available, the root content directory for link validation
Analysis Steps
1. Heading Hierarchy (PQ10)
Parse all headings (H1-H6). Check:
- No skipped levels (H1 → H3 without H2 = violation)
- Exactly one H1 (multiple H1s = violation)
- Logical nesting (H2s under H1, H3s under H2)
2. Section Balance (PQ11)
Measure the word count of each H2 section. Calculate:
- Average section length
- Max section / average ratio (>2x = violation)
- Min section / average ratio (<0.3x = potentially thin section)
3. Intro + Conclusion (PQ12)
Check:
- Content exists before the first H2 (intro paragraph)
- Last section has a concluding or CTA character
4. Protected Region Detection
Scan the file for regions that must NOT be modified during optimization:
Code blocks:
- Count fenced code blocks (``` markers)
- Record start/end line numbers
MDX components:
- Detect import statements at file start (
import ... from ...) - Detect JSX/component tags (
<ComponentName ... />or<ComponentName>...</ComponentName>) - Record component names and line positions
Complex frontmatter:
- Parse YAML frontmatter
- Identify fields that are safe to optimize:
title,description,keywords,author - Identify fields that must be preserved: everything else (arrays, nested objects, relational IDs)
- Count preservable fields
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.
- 2d ago First seen · 116 lines · 21 tokens per session scan A e7d9897c6f11
structure-analyst is an agent published in the GitHub repository greglas75/zuvo (6 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 853 once invoked, about $0.0001 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
ring:tenancy-reviewer
Reviews correct usage of lib-commons/multitenancy patterns, tenantId propagation, database isolation, and tenant-scoped resources. Runs in parallel with other reviewers.
ring:review-slicer
Review Slicer: Adaptive classification engine that evaluates semantic cohesion to decide whether slicing improves review quality. Sits between Mithril pre-analysis and reviewer dispatch. Classification-only — does NOT read source code.
ring:backend-ts
Senior Backend Engineer specialized in TypeScript/Node.js for scalable systems. Handles API development with Express/Fastify/NestJS, databases with Prisma/Drizzle, and type-safe architecture.
ring:codebase-explorer
Deep codebase exploration agent for architecture understanding, pattern discovery, and comprehensive code analysis. Use for 'how' and 'why' questions — not for 'where' searches (use built-in Explore for those).
ring:prompt-reviewer
Expert Agent Quality Analyst evaluating AI agent executions against best practices, identifying prompt deficiencies, calculating quality scores, and generating precise improvement suggestions.
ring:qa
Senior QA Analyst for financial systems. Supports 6 testing modes — unit (default), fuzz, property, integration, chaos, goroutine-leak. Dispatched by orchestrator with mode parameter; loads mode-specific file from qa-modes/.