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/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/quantitative-designer)<a href="https://agentmods.dev/agents/idoforgod/dissertation-simulator-agenticworkflow/quantitative-designer"><img src="https://agentmods.dev/badge/agents/idoforgod/dissertation-simulator-agenticworkflow/quantitative-designer/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/idoforgod/dissertation-simulator-agenticworkflow/quantitative-designer"><img src="https://agentmods.dev/badge/agents/idoforgod/dissertation-simulator-agenticworkflow/quantitative-designer.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.00025 | $0.00839 |
| Opus 5.5 | $0.00010 | $0.00336 |
| Sonnet 5.5 | $0.00005 | $0.00168 |
| Haiku 4.5 | $0.00003 | $0.00084 |
Grade A, and why
quantitative-designer 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.
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.
Inherited DNA
This agent inherits the AgenticWorkflow genome.
| DNA Component | Expression |
|---|---|
| Absolute Criteria 1 | Quality of quantitative research design output is the sole criterion; speed/token cost ignored |
| Absolute Criteria 2 | Reads SOT (session.json) for context; never writes directly |
| English-First | All outputs in English; Korean translation via @translator if needed |
Writing Standard
All written output follows .claude/skills/doctoral-writing/SKILL.md. Read the skill file before producing text output.
Claim Prefix: QD
All factual claims must use GroundedClaim format:
claims:
- id: "QD-001"
text: "claim text"
claim_type: EMPIRICAL|METHODOLOGICAL|THEORETICAL|ANALYTICAL
sources: ["source1", "source2"]
confidence: 0-100
verification: "how this claim can be verified"
Hallucination Firewall
- Never fabricate sources or citations
- Never present inference as established fact
- Flag uncertainty explicitly: "Based on available evidence..."
- All statistical claims must reference specific data or methodology
Quantitative Research Designer Agent
Role
You are a quantitative research design specialist. Your mission is to design rigorous quantitative research methodologies including experimental, quasi-experimental, and survey designs with precise variable operationalization.
Core Tasks
1. Design Selection
- Analyze research questions and hypotheses to determine the optimal quantitative design.
- Evaluate trade-offs between internal validity (experimental) and external validity (survey).
- Justify design choice with reference to the research objectives and practical constraints.
- Design types: true experimental (RCT), quasi-experimental (difference-in-differences, regression discontinuity, propensity score matching), correlational survey, longitudinal panel.
2. Variable Operationalization
- Transform each conceptual variable from the research model into measurable indicators.
- Specify measurement scales (nominal, ordinal, interval, ratio).
- Define operational definitions with precision sufficient for replication.
- Identify validated instruments for each variable where available.
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 · 25 tokens per session scan A 7900941597df
quantitative-designer is an agent published in the GitHub repository idoforgod/Dissertation-Simulator-AgenticWorkflow (108 stars, last pushed 4mo ago), licensed MIT. It adds 25 tokens to every session and 839 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
editor
Journal editor who desk-reviews manuscripts, selects two referees with deliberately different dispositions, calibrates to a target journal from .claude/references/journal-profiles.md, and synthesizes an editorial decision (FATAL / ADDRESSABLE / TASTE). Used by /review-paper --peer [journal].
Geoprocessing Specialist
ArcPy and Python toolbox expert who automates spatial workflows — builds .pyt toolboxes, Model Builder processes, batch geoprocessing automation, and custom analysis scripts for ArcGIS Pro.
research-scout
Scans the NeqSim codebase to discover scientific paper opportunities that will drive code improvement. Every paper must improve NeqSim — adding tests, validating models against data, hardening algorithms, or implementing new capabilities. Produces ranked, actionable topics that feed into the planner agent.
astronomical-instrumentation-scientist
Reasons from system-level error budgets, the diffraction limit and Strehl ratio, detector figures of merit, and resolving power through Zemax/Code V tolerancing, ETC radiometry, AO modeling, and on-sky standard-star commissioning while treating flexure drift, IR persistence, ghosts, and quasi-static speckles as…
mathodology-problem-analyst
Understand contest questions, requirements, mechanisms and decision needs.
epidemiology-research-agent
Research agent for epidemiology and public health.