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 agentmods add skills/librefang/librefang-registry/confluencenpx skills add librefang/librefang-registry --skill confluencegit clone --depth 1 https://github.com/librefang/librefang-registryWhat 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 | $0.00018 | $0.00696 |
| Opus 5 | $0.00009 | $0.00348 |
| Sonnet 5 | $0.00004 | $0.00139 |
| Haiku 4.5 | $0.00002 | $0.00070 |
Grade A, and why
confluence 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 2d 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.
This is a copy
95% identical to confluence — 3 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 43 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Confluence Expert
A technical documentation specialist with deep experience organizing knowledge bases, team wikis, and project documentation in Confluence. This skill provides guidance for structuring spaces, designing page hierarchies, leveraging macros effectively, and using the Confluence REST API for automation, ensuring that documentation remains discoverable, maintainable, and useful.
Key Principles
- Structure spaces around teams or projects, not individuals; each space should have a clear owner and a defined scope of content
- Design page hierarchies no more than 3-4 levels deep; deeply nested pages become difficult to navigate and are rarely discovered by readers
- Use labels consistently across spaces to create cross-cutting taxonomies; labels power search, reporting, and content-by-label macros
- Write for scanning: use headings, bullet points, status macros, and expand sections so readers can quickly find what they need without reading entire pages
- Maintain content hygiene with regular reviews; assign page owners and archive stale documentation to prevent knowledge rot
Techniques
- Create space home pages with a clear navigation structure using the Children Display macro, Content by Label macro, and pinned links to key pages
- Use the Page Properties macro with Page Properties Report to build structured databases across pages (e.g., runbook registries, decision logs)
- Format content with Info, Warning, Note, and Tip panels to visually distinguish different types of information
- Build tables with the Table of Contents macro for long pages and the Excerpt Include macro to reuse content snippets across multiple pages
- Apply page templates at the space level for consistent formatting of recurring document types (meeting notes, ADRs, postmortems)
- Automate content management through the REST API: GET /rest/api/content for search, POST for page creation, and PUT for updates using storage format XHTML
- Set granular permissions at the space and page level; restrict sensitive pages (HR, security) while keeping general documentation open
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.
- 2d ago First seen · 43 lines · 18 tokens per session scan A 79e98ea603a0
confluence is a skill published in the GitHub repository librefang/librefang-registry (11 stars, last pushed 8d ago), licensed MIT. It adds 18 tokens to every session and 696 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 95% identical to confluence, differing in 3 lines, and is treated as a copy.
Other skills, from other repositories
wiki_submit
Submit wiki documentation pages to Wegent backend API. Simplifies the HTTP POST process for wiki content submission.
generate-ai-rules
Generate AI assistant configuration files for a repository — CLAUDE.md, AGENTS.md, and Cursor rules (.cursor/rules/.mdc) — from codebase analysis. Use whenever the user wants to create or update CLAUDE.md, AGENTS.md, agent rules, Cursor rules, AI coding assistant configuration, or "onboard AI tools" to a project, even…
summarize
Summarize conversations, logs, docs, or investigation notes into action-oriented text with evidence tags. Use for recap, handoff, CI failure digest, or MEMORY. Triggers: 总结, 汇总, summarize, 交接, 复盘, 调试总结.
github
Prepare GitHub issues, pull requests, reviews, and release notes for Zhin projects. Use when asked to write an issue, PR description, changelog entry, or review comment. Triggers: 写 issue, PR 描述, 提 PR, release notes, gh pr.
skill-creator
Create or improve Zhin Agent skills (SKILL.md). Use when asked to add a skill, write SKILL.md, document a repeatable agent workflow, or refine skill frontmatter/keywords. Triggers: 创建技能, 写 SKILL, skill-creator, 加 skill.
military-manual
标准化流程，最佳实践，操作指南.