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/coauthor-credit)<a href="https://agentmods.dev/commands/abhinavbwj/aec-scholar/coauthor-credit"><img src="https://agentmods.dev/badge/commands/abhinavbwj/aec-scholar/coauthor-credit/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/coauthor-credit"><img src="https://agentmods.dev/badge/commands/abhinavbwj/aec-scholar/coauthor-credit.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.00017 | $0.00414 |
| Opus 5 | $0.00009 | $0.00207 |
| Sonnet 5 | $0.00003 | $0.00083 |
| Haiku 4.5 | $0.00002 | $0.00041 |
Grade A, and why
coauthor-credit 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 12d 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
Help assign authorship and contributor credit for: $ARGUMENTS
Use the research-ethics-integrity skill. This is integrity-sensitive — be principled, not political.
-
Authorship eligibility. Assess each contributor against ICMJE-style criteria (substantial contribution to conception/design or data/analysis; drafting/revising critically; final approval; accountability — typically all four). Identify who qualifies as an author and who belongs in Acknowledgements (funding-only, supervision-only, general support, or technical help that doesn't meet the bar).
-
Flag problems. Name and caution against gift/guest/ghost authorship and (in fields that order by contribution) order that misrepresents input. Note that AI tools cannot be authors and their use is disclosed, not credited.
-
CRediT roles. Map each author to the 14 CRediT roles (Conceptualization, Methodology, Software, Validation, Formal analysis, Investigation, Resources, Data curation, Writing – original draft, Writing – review & editing, Visualization, Supervision, Project administration, Funding acquisition). Produce a clean author-contributions statement.
-
Author order. Discuss conventions (first = lead contributor; last = senior/PI in many AEC/engineering groups; corresponding author role) — and recommend the team agree explicitly and early, ideally in writing.
-
Output a draft author list + order, a CRediT contributions statement, and an acknowledgements line.
Be even-handed and base recommendations on stated contributions only. Where input is unclear, ask rather than assume. Flag any arrangement that would breach publication ethics.
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.
- 12d ago First seen · 34 lines · 17 tokens per session scan A 6a2d61bbfee1
coauthor-credit is a command published in the GitHub repository Abhinavbwj/AEC-Scholar (18 stars, last pushed 2mo ago), licensed MIT. It adds 17 tokens to every session and 414 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…
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.
simulation-calibrator
Test and refine simulation accuracy with validation loops, bias detection, and continuous improvement frameworks.
arg-diagram
ARG academic-paper diagram mode — standalone structural & conceptual diagram generation.
graphite-morphology-classify
Classify graphite in a cast-iron micrograph per ASTM A247 / ISO 945-1, quantify nodularity, and read the matrix — the single most diagnostic observation in a cast-iron case.