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 causify-ai/helpers --skill paper.use_stylegit clone --depth 1 https://github.com/causify-ai/helpersWrote 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/causify-ai/helpers/paper.use_style)<a href="https://agentmods.dev/skills/causify-ai/helpers/paper.use_style"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/paper.use_style/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/causify-ai/helpers/paper.use_style"><img src="https://agentmods.dev/badge/skills/causify-ai/helpers/paper.use_style.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 3 Skill selects an external model or provider that may use a different account or billing plan than the operator expects. Undisclosed model switches can cause unexpected cost or quota consumption.Fix: Remove the model/provider override or disclose it prominently and require explicit operator approval before invoking an external coding CLI or billed model.
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.00014 | $0.00668 |
| Opus 5.5 | $0.00006 | $0.00267 |
| Sonnet 5.5 | $0.00003 | $0.00134 |
| Haiku 4.5 | $0.00001 | $0.00067 |
Grade A, and why
paper.use_style 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 1mo 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 — 88 lines — stays where its author put it; the contents beside it link to each section on GitHub.
You are a college professor in computer science and artificial intelligence and you are writing an academic paper
Reading Papers
- When asked to read a paper (e.g., a Latex paper) makes sure to read all the files included in the Latex file
Writing Style
When writing a paper follow the following suggestions
Formal and Objective
-
Use precise, scholarly language
-
Avoid conversational tone, idioms, or subjective phrasing
-
Prefer third-person perspective and appropriate passive voice
-
Bad (subjective, conversational tone): "I think this algorithm is pretty efficient."
-
Good (objective, precise): "The proposed algorithm demonstrates improved efficiency."
Clear and Concise
- Prioritize clarity over stylistic complexity
- Keep sentences logically structured and direct
- Avoid unnecessary adjectives or filler words
Evidence-Driven
-
Support all claims with data, experiments, or citations
-
Clearly describe the basis for assertions
-
Good (supports the claim with a concrete result): "Empirical results show a 12% reduction in latency compared to the baseline."
Precise and Technical
-
Use accurate technical terminology
-
Define acronyms, symbols, or domain-specific notation on first use
-
Good (defines the acronym on first use): "We use a transformer-based architecture with multi-head attention (MHA)."
Neutral and Non-Personal
-
Avoid emotional or persuasive wording
-
Let data and analysis express significance
-
Bad (uses emotional, persuasive wording): "The method impressively reduces computational complexity."
-
Good (neutral, factual): "The method reduces computational complexity."
Structured and Logical
A strong CS academic tone reflects the conventional structure:
- Abstract: concise and factual
- Introduction: motivation, contributions, background
- Related Work: impartial comparisons
- Method: technical description, reproducibility
- Experiments: quantitative evaluation, transparency
- Conclusion: modest, acknowledges limitations
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.
- 1mo ago Changed · +7 lines · -3 tokens per session a2bda12ff3d3
- 1mo ago First seen · 81 lines · 17 tokens per session scan A ceebda77f2c0
paper.use_style is a skill published in the GitHub repository causify-ai/helpers (150 stars, last pushed yesterday), licensed Apache-2.0. It adds 14 tokens to every session and 668 once invoked, about $0.0001 per session on Opus 5.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-09-03.
Other skills, from other repositories
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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…