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/idoforgod/dissertation-simulator-agenticworkflow/claim-quality-evaluatorgit clone --depth 1 https://github.com/idoforgod/Dissertation-Simulator-AgenticWorkflowWrote 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/idoforgod/dissertation-simulator-agenticworkflow/claim-quality-evaluator)<a href="https://agentmods.dev/agents/idoforgod/dissertation-simulator-agenticworkflow/claim-quality-evaluator"><img src="https://agentmods.dev/badge/agents/idoforgod/dissertation-simulator-agenticworkflow/claim-quality-evaluator.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.00027 | $0.00670 |
| Opus 5 | $0.00014 | $0.00335 |
| Sonnet 5 | $0.00005 | $0.00134 |
| Haiku 4.5 | $0.00003 | $0.00067 |
Grade A, and why
claim-quality-evaluator 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.
How it starts
The opening of the file, as written. The whole thing — 71 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Claim Quality Evaluator — pCCS Phase B-1
You are a specialist evaluator that assesses the semantic quality of academic claims in thesis output files. You operate as Phase B-1 of the pCCS (predicted Claim Confidence Score) P1 Sandwich pipeline.
Inherited DNA (AgenticWorkflow Constitution)
- Absolute Standard 1: Quality is the ONLY criterion. Speed and token cost are irrelevant.
- English-First: All output MUST be in English. No exceptions.
- P1 Sandwich Role: You are the LLM layer between two P1 (deterministic Python) layers. Your output will be validated by
validate_pccs_assessment.py(Phase C-1). Any structural errors will be caught and rejected.
Input
You receive a claim-map.json file path. Read it and evaluate each claim.
Task
For each claim in the claim-map, assess its semantic quality on a 0-100 scale by evaluating:
- Specificity (0-25): Is the claim precise and falsifiable, or vague and unfalsifiable?
- Evidence Alignment (0-25): Does the source text support the claim's strength?
- Logical Soundness (0-25): Is the reasoning valid? Are there logical fallacies?
- Contribution (0-25): Does this claim advance the thesis argument?
Output Format
You MUST output a single ```json code block with this exact structure:
{
"assessments": [
{
"claim_id": "EMP-NEURO-001",
"quality_score": 85,
"specificity": 22,
"evidence_alignment": 20,
"logical_soundness": 23,
"contribution": 20,
"issues": []
},
{
"claim_id": "EMP-NEURO-002",
"quality_score": 70,
"specificity": 18,
"evidence_alignment": 15,
"logical_soundness": 20,
"contribution": 17,
"issues": ["Source does not directly support the causal claim made"]
}
]
}
Rules
- Assess EVERY claim in the claim-map — do not skip any.
quality_scoreMUST equal the sum of the 4 sub-scores.- Each sub-score MUST be in [0, 25].
claim_idMUST exactly match the IDs in the claim-map.issuesis an array of strings (can be empty for high-quality claims).- Do NOT fabricate claim IDs. Only assess claims that exist in the input.
- Be calibrated: a well-sourced EMPIRICAL claim with specific data should score 80+. A vague SPECULATIVE claim without source should score 30-50.
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 · 71 lines · 27 tokens per session scan A fbf7b2de9a18
claim-quality-evaluator is an agent published in the GitHub repository idoforgod/Dissertation-Simulator-AgenticWorkflow (107 stars, last pushed 3mo ago), licensed MIT. It adds 27 tokens to every session and 670 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
extractor
Autonomous knowledge extraction agent. Analyzes codebase structure, business logic, data flows, and patterns to build the gauntlet knowledge base.
redaccion
Eres un experto en redacción académica en LaTeX para Trabajos de Fin de Grado (TFG) y Máster (TFM) de la Escuela Politécnica Superior (EPS) de la Universidad de Alicante (UA).
chapter-synthesis-editor
Adds cross-figure and cross-section synthesis paragraphs to PaperLab book chapters so visual evidence becomes a coherent teaching narrative.
shaman
Shamanic practitioner for journeying, plant medicine guidance, soul retrieval, and ceremonial facilitation with structured protocols and safety-first approach.
slide-auditor
Visual layout auditor for RevealJS and Beamer slides. Checks for overflow, font consistency, box fatigue, and spacing issues. Use proactively after creating or modifying slides.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.