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 commands/abhinavbwj/aec-scholar/methodologygit clone --depth 1 https://github.com/Abhinavbwj/AEC-ScholarWrote 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/commands/abhinavbwj/aec-scholar/methodology)<a href="https://agentmods.dev/commands/abhinavbwj/aec-scholar/methodology"><img src="https://agentmods.dev/badge/commands/abhinavbwj/aec-scholar/methodology.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.1 | $0.00014 | $0.00433 |
| Opus 5 | $0.00007 | $0.00217 |
| Sonnet 5 | $0.00003 | $0.00087 |
| Haiku 4.5 | $0.00001 | $0.00043 |
Grade A, and why
methodology 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.
What it actually says
Design a methodology for: $ARGUMENTS
Use the methodologist agent and the research-methods skill (plus research-ethics-integrity for the
ethics gate and aec-domains for domain fit).
Produce a structured methodology the user can adapt into a methods chapter:
-
Method choice + justification. Select the method family (survey, experiment/quasi-experiment, case study, interviews, mixed methods, design science, Delphi, simulation/modeling, MCDM) that fits the question, and justify it against alternatives. Name the paradigm.
-
Research design. Detail the design (e.g., single vs multiple case; convergent vs sequential mixed; DSR build–demonstrate–evaluate cycle; simulation calibration/validation plan).
-
Data & sampling. Data sources, sampling strategy and justified size (power analysis / saturation / SEM ratios / Delphi panel), inclusion/exclusion.
-
Instruments & procedure. Instruments/tools (with versions), protocol, and step-by-step procedure detailed enough to reproduce.
-
Analysis plan. How data will be analyzed (hand off to
/aec-scholar:data-analysisfor depth). -
Validity, reliability & rigor. The specific checklist for the chosen method (internal/external/ construct validity & reliability; or qualitative trustworthiness; or verification/validation + uncertainty/sensitivity for simulation). Explicitly address generalizability limits.
-
Ethics & reproducibility. IRB/consent/GDPR/site confidentiality as applicable, and a data/code availability plan.
-
Threats to validity. A candid section listing threats and mitigations.
Flag the AEC-recurring weaknesses (unvalidated models, single-case over-generalization, small ML datasets) and design around them. Provide a clean research-workflow description (and offer a Mermaid diagram).
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 · 39 lines · 14 tokens per session scan A 02921521d40f
methodology is a command published in the GitHub repository Abhinavbwj/AEC-Scholar (18 stars, last pushed 2mo ago), licensed MIT. It adds 14 tokens to every session and 433 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 commands, from other repositories
verify-math
Verify a self-authored mathematical result end to end by routing claims across adversarial review, numerical falsification, symbolic or CAS checks, and Lean, then aggregating one report. Use when a theorem, proposition, conjecture, or paper-wide mathematical argument needs the appropriate combination of verification…
master_analysis
Run comprehensive 5-phase analysis across labs, genetics, and protocols.
replication-package
Scaffold or audit a social-science replication package at a target directory, and audit the manuscript and its archived research objects against FAIR principles.
diff
Quantitative volume comparison between a CadQuery model and a reference STEP file.
arg-diagram
ARG academic-paper diagram mode — standalone structural & conceptual diagram generation.
simulation-calibrator
Test and refine simulation accuracy with validation loops, bias detection, and continuous improvement frameworks.