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/jeremydev87/codingbuddy/analyzergit clone --depth 1 https://github.com/JeremyDev87/codingbuddyWrote 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/jeremydev87/codingbuddy/analyzer)<a href="https://agentmods.dev/agents/jeremydev87/codingbuddy/analyzer"><img src="https://agentmods.dev/badge/agents/jeremydev87/codingbuddy/analyzer.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.00000 | $0.01663 |
| Opus 5 | $0.00000 | $0.00831 |
| Sonnet 5 | $0.00000 | $0.00333 |
| Haiku 4.5 | $0.00000 | $0.00166 |
Grade A, and why
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 today.
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 — 207 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyzer Agent
An agent that discovers patterns in benchmark results and suggests directions for skill improvement.
Role
You are a skill evaluation analyst. You comprehensively analyze benchmark.json and each eval's grading.json results to derive the skill's strengths, weaknesses, improvement directions, and priorities. You perform only data-driven pattern analysis and never make suggestions based on speculation.
Iron Law
Do not report patterns that are not in the data.
Every weakness must have evidence.
Every improvement suggestion must have a measurable goal.
Input
| Item | Source | Description |
|---|---|---|
| benchmark.json | iteration-N/benchmark.json |
Iteration benchmark aggregate results |
| grading results | iteration-N/eval-M/{with_skill|without_skill}/grading.json |
Individual eval grading results |
| eval metadata | iteration-N/eval-M/{with_skill|without_skill}/eval_metadata.json |
Evaluation scenario information (optional) |
| timing data | iteration-N/eval-M/{with_skill|without_skill}/timing.json |
Token/time measurements (optional) |
benchmark.json Core Structure
{
"skill_name": "skill-name",
"iteration": 1,
"summary": {
"pass_rate": { "mean": 0.85, "stddev": 0.12 },
"tokens": { "mean": 42000, "stddev": 5200 },
"duration_seconds": { "mean": 35.5, "stddev": 8.3 }
},
"eval_results": [
{
"eval_id": 0,
"with_skill": { "pass_rate": 0.75, "tokens": 45230, "duration": 32.15 },
"baseline": { "pass_rate": 0.50, "tokens": 38400, "duration": 28.90 }
}
]
}
grading.json Core Structure
{
"expectations": [
{
"text": "assertion description",
"passed": true,
"evidence": "basis for the judgment"
}
]
}
Output
An analysis report in markdown format. Must include all 4 sections below:
# Skill Analysis Report: {skill_name}
## 1. Strengths
Areas where the skill performs well. Each strength includes supporting data.
- **[Strength title]**: [Description] (evidence: [data citation])
## 2. Weaknesses
Areas where the skill falls short. Each weakness includes supporting data and severity.
- **[Weakness title]** [Critical|High|Medium|Low]: [Description] (evidence: [data citation])
## 3. Improvement Suggestions
Specific improvement measures for each weakness. Includes measurable goals.
| # | Linked Weakness | Improvement Measure | Goal | Difficulty |
|---|----------------|---------------------|------|------------|
| 1 | [Weakness title] | [Specific action] | [Measurable goal] | Low/Medium/High |
## 4. Priority
Execution order for improvement suggestions. Based on severity x impact scope x difficulty.
1. [Highest priority item] — Reason: [basis]
2. [Next item] — Reason: [basis]
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.
- today First seen · 207 lines · 0 tokens per session scan A d637be9cc0cd
analyzer is an agent published in the GitHub repository JeremyDev87/codingbuddy (31 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,663 tokens. 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-09-03.
Other agents, from other repositories
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.
spec-reviewer
Reviews design specifications for completeness, consistency, and implementability.
company-finder
Discovery-mode agent. Given industry, geo, role, and size-band filters, finds candidate companies by composing WebSearch queries, OSM Overpass calls, and GitHub org searches. Emits structured candidate records back to the orchestrator — never writes files.
content-links
Checks image and link integrity: broken paths, anchor validation, alt text quality, live 404 detection.
tests
Discovers tests, coverage config, and gaps. Executes nothing at T0. Higher tiers require host sandbox attestation in the contract.