Borrowing it
Nothing to install: this file belongs to julienkay/com.doji.package-authoring. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/julienkay/com.doji.package-authoring/master/.codex/skills/user-facing-docfx-docs/SKILL.mdgit clone --depth 1 https://github.com/julienkay/com.doji.package-authoringWrote 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/julienkay/com.doji.package-authoring/user-facing-docfx-docs)<a href="https://agentmods.dev/skills/julienkay/com.doji.package-authoring/user-facing-docfx-docs"><img src="https://agentmods.dev/badge/skills/julienkay/com.doji.package-authoring/user-facing-docfx-docs/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/julienkay/com.doji.package-authoring/user-facing-docfx-docs"><img src="https://agentmods.dev/badge/skills/julienkay/com.doji.package-authoring/user-facing-docfx-docs.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.00051 | $0.01853 |
| Opus 5.5 | $0.00020 | $0.00741 |
| Sonnet 5.5 | $0.00010 | $0.00371 |
| Haiku 4.5 | $0.00005 | $0.00185 |
Grade A, and why
user-facing-docfx-docs scanned grade A with 1 finding 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 2mo 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
- Do not assume HTTP checks from the current Codex session can reach a DocFX server started by another session. Session-local `curl` failures do not prove the preview is stale or broken. How it starts
The opening of the file, as written. The whole thing — 166 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User-Facing DocFX Docs
Use this skill when editing docs/ for package consumers.
Audience split
Keep user-facing docs focused on using the package:
- what the tool does
- when to use each workflow
- what each visible setting changes
- what files or output the user should expect
Keep maintainer-only material out of consumer docs.
Source of truth
Do not guess from UI text alone. Verify against implementation before documenting behavior.
Read only the files needed for the current page, usually:
- wizard window classes in
com.doji.package-authoring/Editor/Wizards/ - settings models in
com.doji.package-authoring/Editor/Wizards/Models/ - drawers and shared GUI in
com.doji.package-authoring/Editor/Wizards/Drawers/and.../UI/ - template providers and template classes in
.../Presets/and.../Templates/
Document actual behavior, including:
- conditional fields
- foldouts and hidden sections
- generated files and folders
- token support
- side effects in manifests or project output
Documentation standards
Prefer task-oriented docs first, then reference depth:
- Landing page with workflow map
- Task pages for major tools
- Reference pages for dense UI surfaces such as wizard settings
- Supporting pages for templates, presets/defaults, and generated output
Before rewriting a page or section, decide these three things privately:
- Where does this page sit in the docs flow?
- What job should this section do for the future reader?
- What is the main point the reader must leave with?
Reflect those answers through refactoring, not explanation:
- change headings so they carry the right question or topic
- move sections so the reader gets orientation before detail
- cut repetition that does not help a decision or action
- replace vague framing with concrete effects, outputs, paths, or UI behavior
Write to the future reader of the docs, not to the current user prompt:
- avoid meta lines such as "this page explains" or "the goal of this page is" unless the orientation is genuinely useful
- do not narrate your documentation strategy inside the docs
- show the important consequence directly instead of explaining that you are about to explain it
- if a sentence sounds like reassurance to the requester rather than guidance to the product user, rewrite or delete it
- prefer refactoring-style fixes to the prose: rename headings, reorder sections, tighten labels, or replace meta sentences with direct content
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.
- 2mo ago First seen · 166 lines · 51 tokens per session scan A cb74e15e4267
user-facing-docfx-docs is a skill published in the GitHub repository julienkay/com.doji.package-authoring (5 stars, last pushed 5mo ago), licensed MIT. It adds 51 tokens to every session and 1,853 once invoked, about $0.0002 per session on Opus 5.5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
user-facing-docfx-docs compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| user-facing-docfx-docsjulienkay/com.doji.package-authoring | Skill | 5 | 5mo ago | MIT | A | 51 | Codex |
| imagegenopenai/codex | Skill | 133k | yesterday | Apache-2.0 | A | 113 | Codex |
| playwright-climicrosoft/playwright | Skill | 99k | yesterday | Apache-2.0 | A | 19 | Claude Code |
| local-ai-agentsmicrosoft/ai-agents-for-beginners | Skill | 79k | 4d ago | MIT | A | 200 | Claude Code, Codex |
| systematic-debuggingobra/superpowers | Skill | 313k | 3d ago | MIT | A | 21 | Claude Code |
| next-cache-components-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 95 | Claude Code |
| next-partial-prefetching-adoptionvercel/next.js | Skill | 143k | yesterday | MIT | A | 103 | Claude Code |