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/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/research-gap)<a href="https://agentmods.dev/commands/abhinavbwj/aec-scholar/research-gap"><img src="https://agentmods.dev/badge/commands/abhinavbwj/aec-scholar/research-gap/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/commands/abhinavbwj/aec-scholar/research-gap"><img src="https://agentmods.dev/badge/commands/abhinavbwj/aec-scholar/research-gap.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.00016 | $0.00451 |
| Opus 5 | $0.00008 | $0.00226 |
| Sonnet 5 | $0.00003 | $0.00090 |
| Haiku 4.5 | $0.00002 | $0.00045 |
Grade A, and why
research-gap 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 9d 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
Identify research gaps for: $ARGUMENTS
Use the aec-domain-expert agent and the aec-domains skill. If the user pasted papers/abstracts or a
prior review, ground the analysis in them; otherwise reason from the field's known state and be explicit that
the user must validate against a real search.
Produce:
-
State of the art (brief). What is reasonably well established in this area.
-
Gap taxonomy. Classify candidate gaps by type:
- Evidence gaps (contradictory or insufficient findings),
- Knowledge/theoretical gaps (unexplained mechanisms, missing frameworks),
- Methodological gaps (weak validation, single-case over-generalization, small/biased datasets — AEC's chronic weaknesses),
- Population/context gaps (untested building types, regions, project scales, climates),
- Practical/implementation gaps (technically shown but not adoption-tested),
- Intersection gaps (cross-field combinations — e.g. BIM×LCA, vision×safety, generative design×embodied
carbon, LLMs×compliance checking; pull from
aec-domains).
-
Prioritized agenda. For the 3–5 most promising gaps, give: a sharp problem statement, why it matters (scholarly + industry), feasibility, likely method (link to
research-methods), and a candidate venue (aec-journals). Favor defensible, under-crowded gaps over hype. -
Next step. Offer to turn a chosen gap into research questions (
/aec-scholar:research-question) or a methodology (/aec-scholar:methodology).
Integrity: distinguish gaps you can support from the literature versus hypotheses to verify. Don't claim "no one has studied X" without basis — say "a targeted search is needed to confirm the gap" and specify it.
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.
- 9d ago First seen · 35 lines · 16 tokens per session scan A 7b3d550325bd
research-gap is a command published in the GitHub repository Abhinavbwj/AEC-Scholar (18 stars, last pushed 2mo ago), licensed MIT. It adds 16 tokens to every session and 451 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
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.