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/viva)<a href="https://agentmods.dev/commands/abhinavbwj/aec-scholar/viva"><img src="https://agentmods.dev/badge/commands/abhinavbwj/aec-scholar/viva/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/viva"><img src="https://agentmods.dev/badge/commands/abhinavbwj/aec-scholar/viva.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.00015 | $0.00429 |
| Opus 5 | $0.00008 | $0.00215 |
| Sonnet 5 | $0.00003 | $0.00086 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
viva 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
Prepare the user for their viva / thesis defense: $ARGUMENTS
Use the research-strategist and peer-reviewer agents and the thesis-dissertation skill.
-
Contribution statement. Help the user articulate a crisp 3–5 minute summary of the thesis's original contribution and how the studies connect (the "golden thread").
-
Anticipated questions. Generate a realistic question bank across the categories examiners use:
- Contribution & originality — "What is your original contribution? Why does it matter?"
- Method & rigor — "Why these methods? What are the alternatives you rejected and why?"
- Validity & limitations — "What are the threats to validity? How far do your findings generalize?" (AEC examiners press hard on generalizability — single case/building/simulation.)
- Integration — "How do your chapters/papers fit together?"
- Positioning — "How does this differ from [key prior work]?"
- Reflexivity — "What would you do differently? What's next?"
- Practical relevance — "What does industry do with this?" For each, draft a strong, honest model answer and the key points to hit.
-
Know the weak points first. Surface the thesis's most likely lines of attack (unvalidated assumptions, sample/scale, over-claims) and prepare measured, non-defensive responses + an errata list.
-
Rehearsal. Offer to run a mock viva — ask questions one at a time, let the user answer, and give constructive feedback on substance and framing.
Tone: build genuine confidence through preparation, not bravado. Encourage honest acknowledgment of limitations over defensiveness.
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 · 33 lines · 15 tokens per session scan A 2f6500f781c5
viva is a command published in the GitHub repository Abhinavbwj/AEC-Scholar (18 stars, last pushed 2mo ago), licensed MIT. It adds 15 tokens to every session and 429 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
review
Cold re-quiz on code that already shipped — your own session commits, not the change in front of you.
learn-story-flow
Learn story-flow concepts with interactive guidance for junior developers.
annex-a-deep-dive
Deep dive analysis of ISO 27001 Annex A control domains with implementation guidance.
start-10-1
A guided lesson on setting up clasp, a command-line tool for managing Google Apps Script projects, and connecting it to Google’s Apps Script API.
start-13-4.en
Welcome to Lesson 13-4: Landing Page Implementation!
start-0-8
A Japanese-language command that displays the current project setup progress.