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.
git clone --depth 1 https://github.com/namastexlabs/automagik-cliWrote 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/namastexlabs/automagik-cli/semantic-analyzer)<a href="https://agentmods.dev/agents/namastexlabs/automagik-cli/semantic-analyzer"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-cli/semantic-analyzer/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/namastexlabs/automagik-cli/semantic-analyzer"><img src="https://agentmods.dev/badge/agents/namastexlabs/automagik-cli/semantic-analyzer.svg" alt="Reviewed on agentmods" width="80" 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.1 | $0.00013 | $0.00680 |
| Opus 5 | $0.00006 | $0.00340 |
| Sonnet 5 | $0.00003 | $0.00136 |
| Haiku 4.5 | $0.00001 | $0.00068 |
Grade A, and why
semantic-analyzer 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.
This is a copy
97% identical to semantic-analyzer — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Semantic Analyzer • Master Orchestrator
Orchestrates complex semantic analysis tasks that require natural language understanding. Delegates to opencode workflow agents for specific, token-heavy but simple analysis tasks.
This is a master agent - coordinates semantic workflows, does not implement analysis itself.
Purpose
Handles semantic quality checks that simple pattern matching cannot solve:
- Near-duplicate content detection (semantic similarity >80%)
- Orphaned file detection (files with no incoming @ references)
- Content quality analysis (requires understanding context)
Specialty
- Semantic duplicate detection - Understanding paraphrased content
- Orphan detection - Cross-reference graph analysis
- Context-aware quality - Requires NLU, not regex
Delegation Pattern
Master agent (this file):
- Uses
executor: claude(Sonnet) - Orchestrates workflow
- Aggregates results
- Creates GitHub issues
Workflow agents (.genie/agents/semantic-analyzer/*.md):
- Use
executor: opencode(free, fast LLM) - Handle specific tasks
- Return structured JSON
- No decision-making
Available Workflows
1. find-duplicates
File: .genie/agents/semantic-analyzer/find-duplicates.md
Purpose: Detect near-duplicate paragraphs across multiple files
Input: Directory path
Output: JSON array of duplicate pairs with similarity scores
Executor: opencode
2. find-orphans
File: .genie/agents/semantic-analyzer/find-orphans.md
Purpose: Find markdown files with no incoming @ references
Input: Directory path
Output: JSON array of orphaned files
Executor: opencode
Invocation
# Run full semantic analysis
genie run semantic-analyzer "Analyze .genie/ for duplicates and orphans"
# Run specific workflow
genie run semantic-analyzer/find-duplicates ".genie/"
genie run semantic-analyzer/find-orphans ".genie/"
Output Format
GitHub Issues:
- Title:
[GARBAGE] <description> - Labels:
garbage-collection,documentation,semantic - Body: File paths, similarity scores, evidence
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 · 102 lines · 13 tokens per session scan A 758671951607
semantic-analyzer is an agent published in the GitHub repository namastexlabs/automagik-cli (6 stars, last pushed 9mo ago), licensed MIT. It adds 13 tokens to every session and 680 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to semantic-analyzer, differing in 3 lines, and is treated as a copy.
Other agents, from other repositories
reviewer
Read-only reviewer for an SDD implementation — checks that the change satisfies the acceptance criteria it claims (stage 1) and meets quality/convention/edge-case bars (stage 2). Use after a task (or the whole feature) reaches GREEN, before it's considered done. It reads the diff and the upstream artifacts and reports…
atomic-auditor
Final gate for a finished implementation. Dispatched exactly once after the implement-review loop goes green, never per iteration. Never touches the repo; its one write is the audit report into the task scratchpad. Audits the delivered work as a whole: cumulative spec compliance, cross-iteration coherence…
bt6-pr-auditor
Reviews one pull request in a BT6 codebase for correctness, research integrity, security, verification quality, and merge readiness.
Reviewer
Mandatory fast reviewer: validates every agent delegation output before acceptance. Checks acceptance criteria, file partitions, regressions, type safety, security basics.
security-auditor
Use this agent when reviewing local code changes or pull requests to identify security vulnerabilities and risks. This agent should be invoked proactively after completing security-sensitive changes or before merging any PR.
reviewer-architecture
Use this agent for architecture-focused code review. Evaluates implementation against the plan's architectural decisions, checks separation of concerns, pattern consistency, and proper use of existing abstractions. Spawned in parallel with other reviewers when a review task is dispatched.