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 related-work-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/related-work-writer)<a href="https://agentmods.dev/skills/haohaha-11/paper-writing/related-work-writer"><img src="https://agentmods.dev/badge/skills/haohaha-11/paper-writing/related-work-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/related-work-writer"><img src="https://agentmods.dev/badge/skills/haohaha-11/paper-writing/related-work-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.00835 |
| Opus 5 | $0.00000 | $0.00417 |
| Sonnet 5 | $0.00000 | $0.00167 |
| Haiku 4.5 | $0.00000 | $0.00084 |
Grade A, and why
related-work-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 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.
How it starts
The opening of the file, as written. The whole thing — 113 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Related Work Writer
Purpose
Create related work that is citation-grounded, fair to prior papers, and useful for positioning the current contribution. The goal is not to list papers; it is to explain the intellectual neighborhood of the paper and why the current work is still needed.
When To Use
- Building Related Work from a bibliography and paper context.
- Checking whether recent target-venue papers are missing.
- Revising unfair or vague comparisons.
- Preparing reviewer-facing novelty and baseline defenses.
Inputs
Required:
- paper thesis and contribution map;
- target venue and adjacent venues;
- current bibliography or must-cite list;
- direct competitors;
- method/task/dataset keywords.
Optional:
- cspapers-assisted review output;
- paper-qa or local PDF notes;
- reviewer comments about missing citations;
- venue-specific baseline expectations.
Procedure
-
Build a taxonomy. Group prior work by technical axis, task, dataset, modeling assumption, or evaluation protocol. Avoid pure chronology.
-
Identify comparison roles. Mark each cited work as direct competitor, background, tool, dataset, baseline, theory, or role model.
-
Verify citation support. Each citation should support the sentence it appears in. Mark unchecked citations.
-
Search for missing work. Use cspapers.org and other sources to find recent target-venue or adjacent-venue papers.
-
Write contrastive positioning. For each group, say what prior work established, what limitation remains, and how this paper differs.
-
Connect to experiments. Direct competitors and baselines named in Related Work should be reflected in Experiments when appropriate.
-
Remove unfair claims. Replace "fails to" or "cannot" with precise, evidence-backed limitations unless the prior paper explicitly shows the failure.
Rubric
| Dimension | Strong | Weak |
|---|---|---|
| Organization | Conceptual taxonomy | Chronological paper list |
| Citation grounding | Sentence-level support | Decorative citation clusters |
| Fairness | Accurate limits of prior work | Strawman comparisons |
| Recency | Includes recent target-venue work | Mostly old or convenient citations |
| Positioning | Explains why this paper is needed | Says "different" without reason |
| Baseline link | Competitors map to experiments | Related Work and Experiments disconnected |
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 · 113 lines · 0 tokens per session scan A bbf7491fc157
related-work-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 835 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…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
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…