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 a-attia/scicomp-research-skills --skill human-facing-doc-authoringgit clone --depth 1 https://github.com/a-attia/scicomp-research-skillsWrote 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/a-attia/scicomp-research-skills/human-facing-doc-authoring)<a href="https://agentmods.dev/skills/a-attia/scicomp-research-skills/human-facing-doc-authoring"><img src="https://agentmods.dev/badge/skills/a-attia/scicomp-research-skills/human-facing-doc-authoring/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/a-attia/scicomp-research-skills/human-facing-doc-authoring"><img src="https://agentmods.dev/badge/skills/a-attia/scicomp-research-skills/human-facing-doc-authoring.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 Prompt Injection · line 285 Large whitespace padding was detected (a block of blank lines or a long run of spaces). This can push injected instructions below or to the right of the visible area so a human reviewer never sees them while the agent still reads them. Manual review of the hidden content is recommended.Fix: Remove the large whitespace padding (blank-line blocks or long space runs) and review any content hidden below or to the right of it. Keep skill files compact and reviewable so no instructions can be
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.00169 | $0.06585 |
| Opus 5 | $0.00084 | $0.03292 |
| Sonnet 5 | $0.00034 | $0.01317 |
| Haiku 4.5 | $0.00017 | $0.00658 |
Grade A, and why
human-facing-doc-authoring 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 — 569 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Human-Facing Doc Authoring
When to load this skill
Load this skill whenever the agent is about to produce or substantially revise a document whose primary audience is a human -- not the agent itself, not a downstream tool. In this ecosystem that includes (non-exhaustive list):
README.md-- top-level human-facing entry point for any project.PLAN.md-- plan-of-record / contract; both humans and agents read.notes/survey_<citekey>.md-- per-paper survey notes; the user reads these when drafting paper sections and when re-orienting after time away.references/_collection_log.md-- bibliography verification audit trail; the user (and reviewers) read this.notes/section_<N>.md-- per-paper-section research notes; the user reads them while drafting the section.notes/impl_<component>.md-- per-component implementation plans; the user reads them before greenlighting code.- Reviewer responses / rebuttals.
- Acknowledgement / contribution / changelog files.
Always load this skill before generating any of the above. Other
skills (literature-survey, research-paper-writing) cross-reference
this one for the structural + stylistic conventions they share.
Do NOT load this skill for:
- editing
AGENTS.mdfiles -- those have the opposite audience (agents). They should be telegraphic and structured, not narrative. - editing source code or code docstrings -- those have their own conventions (governed by the project's coding style).
- editing per-skill
SKILL.mdfiles -- those are agent-facing.
Core principle: human/agent audience split
Every project in this ecosystem keeps two parallel entry-point documents with explicitly different audiences:
| File | Audience | Tone |
|---|---|---|
AGENTS.md |
AI coding agents | Telegraphic, structured, machine-parseable. |
README.md |
Human collaborators | Narrative, indexed, designed to be SCANNED. |
What ships with it
5 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 569 lines · 169 tokens per session scan A 15f014774741
human-facing-doc-authoring is a skill published in the GitHub repository a-attia/scicomp-research-skills (11 stars, last pushed 8d ago), licensed MIT. It adds 169 tokens to every session and 6,585 once invoked, about $0.0008 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…