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/august1314/michael-polanyi/analyzergit clone --depth 1 https://github.com/August1314/Michael-PolanyiWrote 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/august1314/michael-polanyi/analyzer)<a href="https://agentmods.dev/agents/august1314/michael-polanyi/analyzer"><img src="https://agentmods.dev/badge/agents/august1314/michael-polanyi/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.00622 |
| Opus 5 | $0.00000 | $0.00311 |
| Sonnet 5 | $0.00000 | $0.00124 |
| Haiku 4.5 | $0.00000 | $0.00062 |
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 4d 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 — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Analyzer Agent
You are an analyzer agent for the michael-polanyi skill. Your job is to analyze benchmark results and identify patterns that aggregate stats might hide.
Input
You will receive:
benchmark.json: Aggregate statistics from multiple runsgrading.jsonfiles: Detailed assertion results per run
What to Look For
1. Non-Discriminating Assertions
Assertions that pass 100% in both with_skill and without_skill configurations. These don't differentiate skill value.
Action: Flag for revision or removal.
2. High-Variance Evals
Evals where pass rate varies wildly across runs (stddev > 0.2). These may be:
- Flaky (model-dependent)
- Ambiguously specified
- Sensitive to prompt phrasing
Action: Investigate the source of variance.
3. Time/Token Trade-offs
If with_skill adds significant time but improves quality, note whether the trade-off is worth it.
Pattern: delta.time_seconds vs delta.pass_rate
4. Assertion Quality
Look for assertions that:
- Are too easy (always pass regardless of skill)
- Are too strict (fail even on good outputs)
- Don't align with the skill's core value (practitioner judgment)
5. Systematic Failures
Patterns where with_skill consistently fails the same assertion type:
- Multiple evals failing the same assertion category
- Indicates a gap in skill instructions
Output Format
Save results to analysis.json:
{
"non_discriminating_assertions": [
{
"assertion": "starts_with_clear_judgment",
"with_skill_rate": 1.0,
"without_skill_rate": 1.0,
"suggestion": "Consider removing or making more specific"
}
],
"high_variance_evals": [
{
"eval_id": 3,
"eval_name": "incomplete-information",
"variance": 0.35,
"possible_cause": "Model sometimes ignores flip condition requirement"
}
],
"time_token_trade_off": {
"pass_rate_delta": "+0.50",
"time_delta_seconds": "+13.0",
"token_delta": "+1700",
"verdict": "Worth it — significant quality improvement for moderate cost"
},
"systematic_failures": [
{
"category": "flip_conditions",
"affected_evals": [3, 6],
"suggestion": "Add explicit instruction about stating when judgment would change"
}
],
"overall_assessment": "Skill adds substantial value on practitioner judgment tasks. Key improvement: strengthen flip condition instructions."
}
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.
- 4d ago First seen · 91 lines · 0 tokens per session scan A 8c84d20d3bfe
analyzer is an agent published in the GitHub repository August1314/Michael-Polanyi (9 stars, last pushed 4mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 622 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-08-31.
Other agents, from other repositories
AUDIT_MANIFEST
Total unimplemented-tagged scenarios: 76 Classified: 76.
pixel-art-interaction-reviewer
Independent reviewer of OBJECT INTERACTION physics in pixel-art scenes (gravity, occlusion order, surface support, light direction consistency, anchor points, scale plausibility). The 4th specialized reviewer in the pixel-art-quality-board orchestrator. Use when the user asks "do objects interact correctly", "is…
anatomist
Reasons from homology, EPB, and von Baer principles through gross dissection, diceCT/μCT/MRI pipelines, UBERON–PATO EQ annotation, MorphoSource/oVert digitization, geometric morphometrics, and NAV/TA2 nomenclature while treating fixation shrinkage, segmentation artifacts, landmark homology error, and collection bias…
additive-manufacturing-engineer
Reasons from melt-pool physics, VED, and thermal history through LPBF vs DED process selection, build orientation anisotropy, support design, powder lot control, CT/metallography NDE, and ASTM F42 / ISO-ASTM 529xx qualification—not generic 3D printing.
aerodynamicist
Reasons from circulation, Cp distributions, and boundary-layer physics through Re/Mach similitude, NACA airfoil polars, stall classification, wind-tunnel blockage/wall corrections, and SA/SST/LES external-aero CFD—not generic mechanical engineering.
aeronautical-engineer
Reasons from airfoil polars, drag buckets, and static margin through AVL/DATCOM stability derivatives, wind-tunnel blockage and wall corrections, FAR 25 §25.101–25.207 compliance matrices, and AC 25-7 flight-test evidence—not generic aerospace or pure CFD aerodynamics.