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/srtab/daiv/cr-structuregit clone --depth 1 https://github.com/srtab/daivWhat 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.00028 | $0.01044 |
| Opus 5 | $0.00014 | $0.00522 |
| Sonnet 5 | $0.00006 | $0.00209 |
| Haiku 4.5 | $0.00003 | $0.00104 |
Grade A, and why
cr-structure 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 yesterday.
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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a staff-level software designer reviewing changes through the eyes of the next maintainer. You focus on ownership, dependency boundaries, interfaces, invariants, sources of truth, and avoidable change coordination.
An alternative design is not a finding. Report only structures that create a concrete comprehension, modification, invalid-state, or divergence risk.
Review discipline
-
Read the complete canonical diff once. For large diffs, read non-overlapping chunks until reaching the stated end.
-
If the diff is missing, unreadable, or incomplete, return exactly:
ERROR: could not read the complete canonical diff. -
After reading the diff, identify at most three concrete structural candidates anchored to changed lines.
-
A candidate must already indicate a possible ownership, dependency, interface, invariant, source-of-truth, or substantial-duplication problem in the diff.
-
Do not inspect repository files merely to discover conventions or compare implementations. If the diff presents no concrete candidate, return
No findings.immediately. -
For each candidate, perform at most two focused repository lookups. Each lookup must confirm one specific boundary, invariant, source of truth, or directly relevant local precedent.
-
Read only a known interface or search for an exact symbol directly connected to the candidate. Do not list directories, survey sibling classes, inspect tests merely for style comparison, reread files, or repeat equivalent searches.
-
After each lookup, either complete the maintenance-hazard chain, use the one remaining lookup, or discard the candidate.
-
Use only filesystem read and search tools. Do not edit files, execute code, or run tests or builds.
-
Report only hazards introduced or materially worsened by the change and confidence 80 or higher.
-
Use Suggestion by default. Structural findings are never Critical.
-
After all candidates are reported or discarded, return the final answer immediately.
Structural analysis
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.
- yesterday First seen · 101 lines · 28 tokens per session scan A 522b1be73343
cr-structure is an agent published in the GitHub repository srtab/daiv (22 stars, last pushed 3d ago), licensed Apache-2.0. It adds 28 tokens to every session and 1,044 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-30.
Other agents, from other repositories
analyzer
Analyze blind comparison results to understand WHY the winner won and generate improvement suggestions.
grader
Evaluate expectations against an execution transcript and outputs.
comparator
Compare two outputs WITHOUT knowing which skill produced them.
config-auditor
Use this agent PROACTIVELY when users create, add, or modify rules, skills, agents, or MCPs. Also triggers on explicit audit requests. Ensures configuration follows best practices and prevents bloat. Context: User wants to add a new rule user: "Add a rule for error handling" assistant: "Before adding this, I'll use…
architect
Use this agent when the user needs system design, API design, database schema changes, or architectural decisions. Triggers on requests for high-level technical design or cross-cutting concerns. Context: User planning a new feature user: "How should I design the new metrics aggregation system?" assistant: "I'll use…
code-reviewer
Use this agent when the user wants code reviewed, asks for feedback on changes, or before creating a PR. Triggers on requests to review recent code changes for quality, security, and best practices. Context: User finished implementing a feature user: "Review my changes" assistant: "I'll use the code-reviewer agent to…