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/automagik-dev/forgeWrote 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/automagik-dev/forge/semantic-analyzer)<a href="https://agentmods.dev/agents/automagik-dev/forge/semantic-analyzer"><img src="https://agentmods.dev/badge/agents/automagik-dev/forge/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/automagik-dev/forge/semantic-analyzer"><img src="https://agentmods.dev/badge/agents/automagik-dev/forge/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.00673 |
| Opus 5.5 | $0.00005 | $0.00269 |
| Sonnet 5.5 | $0.00003 | $0.00135 |
| Haiku 4.5 | $0.00001 | $0.00067 |
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 1mo 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.
Copies of this mod
2 near-identical copies found in the catalogue:
- semantic-analyzer — 97% identical, 3 lines differ
- semantic-analyzer — 97% identical, 3 lines differ
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.
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.
- 1mo ago First seen · 101 lines · 13 tokens per session scan A 29a3f68b58b1
semantic-analyzer is an agent published in the GitHub repository automagik-dev/forge (92 stars, last pushed 10mo ago), licensed Apache-2.0. It adds 13 tokens to every session and 673 once invoked, about $0.0001 per session on Opus 5.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
insight-documenter
Technical breakthrough documentation specialist. Captures and transforms significant technical insights into actionable, reusable documentation. Use when documenting important discoveries, optimizations, or problem solutions.
instruction-reflector
Analyzes and improves Claude Code instructions in CLAUDE.md. Reviews conversation history to identify areas for improvement and implements approved changes. Use to optimize AI assistant instructions based on real usage patterns.
pr-reviewer
Expert code reviewer for GitHub pull requests. Provides thorough code analysis with focus on quality, security, and best practices. Use when reviewing PRs for code quality and potential issues.
github-issue-fixer
GitHub issue resolution specialist. Analyzes, plans, and implements fixes for GitHub issues with proper testing and PR creation. Use when fixing specific GitHub issues.
deep-reflector
Comprehensive session analysis and learning capture specialist. Analyzes development sessions to extract patterns, preferences, and improvements for future interactions. Use after significant work sessions to capture learnings.
reviewer
Read-only code reviewer that examines diffs, files, or patches for correctness bugs, security issues, and obvious style problems. Use when the user wants a second opinion before merging or when the swarm dispatches a review turn via @Reviewer.