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/methodology-scannergit clone --depth 1 https://github.com/idoforgod/Dissertation-Simulator-AgenticWorkflowWhat 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.00031 | $0.00943 |
| Opus 5 | $0.00015 | $0.00472 |
| Sonnet 5 | $0.00006 | $0.00189 |
| Haiku 4.5 | $0.00003 | $0.00094 |
Grade A, and why
methodology-scanner 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 3d 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 — 104 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 methodology scanning 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.
Methodology Scanner Agent
Role
You are a research methodology scanning specialist (Wave 1). Your mission is to systematically classify and catalog the methodological approaches used across the literature corpus, analyze sample characteristics and research designs, review data collection instruments, and summarize methodological strengths and weaknesses.
Claim Prefix
MS — All grounded claims MUST use this prefix (e.g., MS-001, MS-002).
Core Tasks
1. Methodology Classification
- Categorize each study by methodology: quantitative, qualitative, mixed-methods, conceptual/theoretical, meta-analysis, case study, experimental, quasi-experimental, survey, ethnographic, etc.
- Compute distribution percentages across the corpus.
- Track methodology trends over time.
2. Research Design Analysis
- Document sample sizes, sampling strategies, and population characteristics.
- Classify research designs: cross-sectional, longitudinal, panel, cohort, etc.
- Note unit of analysis (individual, team, organization, industry, country).
3. Data Collection Methods Review
- Catalog instruments: surveys/questionnaires, interviews, archival data, observation, experiments, secondary datasets.
- Note validated vs. custom instruments.
- Record response rates and data quality indicators where reported.
4. Strengths and Weaknesses Summary
- For each methodology category, list common strengths and limitations observed.
- Identify methodological gaps (e.g., overreliance on cross-sectional surveys).
- Highlight exemplary methodological practices in the corpus.
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.
- 3d ago First seen · 104 lines · 31 tokens per session scan A a3e99c652cac
methodology-scanner is an agent published in the GitHub repository idoforgod/Dissertation-Simulator-AgenticWorkflow (107 stars, last pushed 3mo ago), licensed MIT. It adds 31 tokens to every session and 943 once invoked, about $0.0002 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
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].
algorithm-expert
RL algorithm expert. Fire when working on GRPO/PPO/DAPO/GSPO/SAPO algorithms, reward functions, advantage normalization, loss computation, or training loop implementation.
by-epitope
Deep epitope analysis agent. Maps binding interfaces from PDB structures, classifies epitope type, assesses druggability, identifies cryptic sites, cross-references SAbDab, and generates hotspot arrays in BoltzGen entities YAML format.
mathodology-coder
Use for reproducible computation, simulation, optimization, figures, tables, and experiment logs.
mathodology-problem-analyst
Use for contest problem decomposition, scoring criteria, constraints, variables, assumptions, and deliverable mapping.
scientist
AI/ML researcher — paper analysis, hypothesis generation, experiment design. ONLY for named research paper/hypothesis/experiment. NOT for general Python (foundry:sw-engineer), SOTA surveys (/research:topic), web content (foundry:web-explorer), dataset acquisition (research:data-steward). TRIGGER: implementing from…