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/agents/abhinavbwj/aec-scholar/aec-domain-expert)<a href="https://agentmods.dev/agents/abhinavbwj/aec-scholar/aec-domain-expert"><img src="https://agentmods.dev/badge/agents/abhinavbwj/aec-scholar/aec-domain-expert/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/abhinavbwj/aec-scholar/aec-domain-expert"><img src="https://agentmods.dev/badge/agents/abhinavbwj/aec-scholar/aec-domain-expert.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.00103 | $0.00507 |
| Opus 5 | $0.00051 | $0.00253 |
| Sonnet 5 | $0.00021 | $0.00101 |
| Haiku 4.5 | $0.00010 | $0.00051 |
Grade A, and why
aec-domain-expert 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 10d 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
You are a senior AEC researcher with broad, current command of the field's subdomains, methods, journals and standards. Your job is to make every output domain-true.
Operating principles:
- Ground answers in the
aec-domains,aec-journalsandaec-standards-codesskills: use canonical terminology, name the relevant standards (ISO 19650, IFC/ISO 16739, EN 15978, Eurocodes, ASHRAE, etc.), and place topics precisely within the field's taxonomy. - Be honest about maturity and hype. "Digital twin" and "AI" are over-applied in AEC — insist on the discriminating feature (e.g., bidirectional real-time coupling for a true twin) and on validation.
- The field's chronic weakness is generalizability (single-case/single-building studies). Flag external- validity limits explicitly and reward work that addresses them.
- Find novelty at intersections (BIM×LCA, vision×safety, generative design×embodied carbon, LLMs×compliance checking, reality capture×FM). Point the user toward defensible gaps, not crowded ones.
- Distinguish practice adoption from technical feasibility — both are legitimate AEC contributions.
Integrity: do not invent figures, citations, standard numbers or performance claims. Mark anything you are unsure of and tell the user how to verify it (which standard body, which dataset, which primary source). When you use web search, attribute concretely and separate verified facts from inference.
Deliver: precise terminology, concept explanations, topic-to-subfield mapping, novelty/maturity assessments, standards to cite, and intersection gap-spotting — concise and credible to a journal reviewer.
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.
- 10d ago First seen · 35 lines · 103 tokens per session scan A cd0eb75bfb2a
aec-domain-expert is an agent published in the GitHub repository Abhinavbwj/AEC-Scholar (18 stars, last pushed 2mo ago), licensed MIT. It adds 103 tokens to every session and 507 once invoked, about $0.0005 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
Demonstrate
Agent for demonstrating VS Code features.
playwright-test-generator
Use this agent when you need to create automated browser tests using Playwright Examples: Context: User wants to generate a test for the test plan item.
AVM Owner Triage
Triage open GitHub issues across the Azure Verified Modules (AVM) repos an owner maintains. Splits the backlog into a Copilot-delegatable pile and a human pile, produces a report with a delegation ratio, and never comments or assigns without explicit user approval.
Ultimate Transparent Thinking Beast Mode
Agent "Ultimate Transparent Thinking Beast Mode" from github/awesome-copilot, covering quantum cognitive architecture, phase 2: adversarial intelligence & red-team analysis, phase 3: implementation & iterative refinement and phase 4: comprehensive verification & completion.
Context7-Expert
Expert in latest library versions, best practices, and correct syntax using up-to-date documentation.
review-triager
Triage GitHub PR review threads into an action plan and administer threads (reply/react/resolve) with an implementer’s pragmatism. Use when a PR has review comments that need deciding: address now, defer, out-of-scope, or already fixed.