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/flurdy/agent-skills/confluencenpx skills add flurdy/agent-skills --skill confluencegit clone --depth 1 https://github.com/flurdy/agent-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/flurdy/agent-skills/confluence)<a href="https://agentmods.dev/skills/flurdy/agent-skills/confluence"><img src="https://agentmods.dev/badge/skills/flurdy/agent-skills/confluence.svg" alt="Measured on agentmods" 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 | $0.00033 | $0.00912 |
| Opus 5 | $0.00016 | $0.00456 |
| Sonnet 5 | $0.00007 | $0.00182 |
| Haiku 4.5 | $0.00003 | $0.00091 |
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 4d 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 — 123 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Confluence Page Lookup
Fetch content from Confluence pages and their comments via the Atlassian MCP.
Which MCP to use
Confluence lives under the same Atlassian Cloud tenant as Jira. In most setups the Jira MCP (mcp__jira__jira_get) can reach Confluence endpoints too — just pass a Confluence path (/wiki/rest/api/content/...).
Priority order:
mcp__jira__jira_get— preferred, already configured in most environments.mcp__confluence__confluence_get— use if a dedicated Confluence MCP is configured.- If neither tool is available, tell the user and stop — do not try
WebFetchon authenticated Confluence URLs.
All examples below use mcp__jira__jira_get. If you fall back to the dedicated Confluence MCP, the paths are the same; only the tool name changes.
Usage
# Search for a page by title
/confluence search "Authentication Design Doc"
# Get a page by ID
/confluence 123456
# Get a page by URL
/confluence https://myorg.atlassian.net/wiki/spaces/ENG/pages/123456
Instructions
Determine intent from the arguments provided.
1. Search for Pages
If the user provides a search term (not a numeric ID or URL):
mcp__jira__jira_get with:
path: /wiki/rest/api/content/search
queryParams:
cql: 'title ~ "<search term>" OR text ~ "<search term>"'
limit: "10"
jq: '{results: [.results[] | {id: .id, title: .title, space: .space.key, url: ._links.webui}]}'
Present results as a table and ask the user which page to fetch.
2. Get Page Content
If the user provides a page ID or after selecting from search results:
mcp__jira__jira_get with:
path: /wiki/rest/api/content/<pageId>
queryParams:
expand: "body.storage,version,space,ancestors"
jq: '{id: id, title: title, space: space.key, version: version.number, ancestors: [ancestors[].title], body: body.storage.value}'
3. Get Page Comments
If the user asks for comments on a page:
mcp__jira__jira_get with:
path: /wiki/rest/api/content/<pageId>/child/comment
queryParams:
expand: "body.storage,version"
jq: '{comments: [.results[] | {author: .version.by.displayName, date: .version.when, body: .body.storage.value}]}'
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.
- 4d ago First seen · 123 lines · 33 tokens per session scan A 1c3f321f2ddd
confluence is a skill published in the GitHub repository flurdy/agent-skills (7 stars, last pushed 5d ago), licensed MIT. It adds 33 tokens to every session and 912 once invoked, about $0.0002 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-31.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
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…