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 skills add Abhinavbwj/AEC-Scholar --skill academic-writinggit 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/skills/abhinavbwj/aec-scholar/academic-writing)<a href="https://agentmods.dev/skills/abhinavbwj/aec-scholar/academic-writing"><img src="https://agentmods.dev/badge/skills/abhinavbwj/aec-scholar/academic-writing/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/skills/abhinavbwj/aec-scholar/academic-writing"><img src="https://agentmods.dev/badge/skills/abhinavbwj/aec-scholar/academic-writing.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.00104 | $0.01620 |
| Opus 5 | $0.00052 | $0.00810 |
| Sonnet 5 | $0.00021 | $0.00324 |
| Haiku 4.5 | $0.00010 | $0.00162 |
Grade A, and why
academic-writing 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 11d 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.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Academic Writing — Craft Guide
Use this to structure manuscripts, strengthen argument, and match scholarly style. Engineering/AEC venues reward clarity, explicit contribution, and methodological transparency over rhetorical flourish.
1. IMRaD and the shape of a paper
Title → Abstract → Keywords → 1 Introduction → 2 (Background/Literature) → 3 Methods → 4 Results → 5 Discussion → 6 Conclusion → Acknowledgements → Declarations → References → Appendices
The classic "hourglass": broad context → narrow to the specific gap/question → method & findings (narrow)
→ broaden again to implications. Empirical AEC papers follow IMRaD; review papers, DSR papers and
conceptual papers vary (state your structure).
2. Section-by-section
Title
Specific, informative, keyword-rich, honest. State the topic + (often) the contribution/method/context.
Avoid vague ("A study on…"), over-claiming, and undefined acronyms. (See /aec-scholar:title-keywords.)
Abstract (150–250 words typically; check venue)
Structured or unstructured per venue. Cover: context/problem → gap/objective → method → key results (with concrete specifics) → contribution/implication. No citations, no undefined acronyms, no content absent from the paper. The abstract is what gets read and indexed — make it self-contained and concrete (numbers beat adjectives).
Introduction — earn the gap (CARS model, Swales)
- Establish the territory — why this matters (real-world + scholarly relevance; keep brief).
- Establish the niche — what is missing/unresolved/contradictory in prior work (the gap move — be specific and fair; don't strawman the literature).
- Occupy the niche — state objective/RQs/hypotheses, your approach, contribution, and (often) a roadmap. End the introduction with an explicit "This paper contributes…" sentence. Make the gap and contribution unmissable — reviewers look for them first.
Background / Literature review
Synthesize, don't list ("author X said… author Y said…" is a red flag). Organize by theme/concept/
chronology/method. Critically position prior work, build toward your gap, and define key terms & the
conceptual/theoretical framework. (For standalone reviews see systematic-review/bibliometric-analysis.)
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.
- 11d ago First seen · 112 lines · 104 tokens per session scan A 952867d02824
academic-writing is a skill published in the GitHub repository Abhinavbwj/AEC-Scholar (18 stars, last pushed 2mo ago), licensed MIT. It adds 104 tokens to every session and 1,620 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 skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…
next-cache-components-optimizer
Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…
next-partial-prefetching-adoption
Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…