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 Haohaha-11/Paper-Writing --skill introduction-writergit clone --depth 1 https://github.com/Haohaha-11/Paper-WritingWrote 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/haohaha-11/paper-writing/introduction-writer)<a href="https://agentmods.dev/skills/haohaha-11/paper-writing/introduction-writer"><img src="https://agentmods.dev/badge/skills/haohaha-11/paper-writing/introduction-writer/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/haohaha-11/paper-writing/introduction-writer"><img src="https://agentmods.dev/badge/skills/haohaha-11/paper-writing/introduction-writer.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.00000 | $0.00779 |
| Opus 5 | $0.00000 | $0.00390 |
| Sonnet 5 | $0.00000 | $0.00156 |
| Haiku 4.5 | $0.00000 | $0.00078 |
Grade A, and why
introduction-writer 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 — 119 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Introduction Writer
Purpose
Draft or revise an introduction that turns the paper strategy into a persuasive, fair, and evidence-backed story. The introduction should make reviewers understand why the problem matters, what gap remains, what the paper contributes, and how the paper proves it.
When To Use
- Writing the first Introduction.
- Revising a rejected paper's framing.
- Aligning Introduction claims with experiments.
- Shortening or sharpening a long motivation section.
Inputs
Required:
- paper thesis;
- target venue and paper type;
- contribution map;
- available results and figures;
- related-work summary;
- known limitations.
Optional:
- current Introduction;
- novelty-scout report;
- claim-evidence matrix;
- target page budget.
Recommended Paragraph Roles
-
Problem anchor. Start with the concrete task, setting, or failure mode. Avoid generic "X is important" openings.
-
Why existing approaches are insufficient. Describe the gap fairly and specifically. Do not attack prior work without evidence.
-
Key insight. State the mechanism or observation that makes the proposed approach plausible.
-
Approach overview. Explain what the paper does at a high level without implementation overload.
-
Evidence preview. Preview datasets, experiments, theory, systems evaluation, or clinical validation.
-
Contributions. List 2-4 testable contributions, each tied to later evidence.
Procedure
- Identify all promises made by the current introduction.
- Remove promises not supported by the paper.
- Reorder paragraphs so motivation leads to gap, gap leads to insight, insight leads to evidence.
- Make contribution bullets falsifiable.
- Check that each contribution appears later in method/results/discussion.
- Move detailed literature taxonomy to Related Work unless it is necessary for motivation.
- Produce a patch plan instead of a blind rewrite when source text is provided.
Rubric
| Dimension | Strong | Weak |
|---|---|---|
| Opening | Concrete problem and stakes | Generic field overview |
| Gap | Specific and fair | Vague "existing methods fail" |
| Insight | Explains why the method should work | Only names the method |
| Contributions | Testable and evidence-linked | Marketing or implementation list |
| Flow | Each paragraph earns the next | Disconnected background blocks |
| Scope | Clear assumptions and limits | Overclaims broad impact |
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 · 119 lines · 0 tokens per session scan A 346a499079f2
introduction-writer is a skill published in the GitHub repository Haohaha-11/Paper-Writing (3 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 779 tokens. 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-31.
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…