Getting it into your agent
This one installs as part of its plugin. Adding the marketplace and installing the plugin brings it with everything else the plugin ships.
/plugin marketplace add ulises-jeremias/agent-toolkit/plugin install agent-toolkit-completeWrote 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/ulises-jeremias/agent-toolkit/confluence-ops)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/confluence-ops"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/confluence-ops.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.1 | $0.00033 | $0.02253 |
| Opus 5 | $0.00016 | $0.01126 |
| Sonnet 5 | $0.00007 | $0.00451 |
| Haiku 4.5 | $0.00003 | $0.00225 |
Grade A, and why
confluence-ops 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 3d 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 — 318 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Confluence Operations Skill
Cache management, API diagnostics, and operational utilities for Confluence Assistant.
⚠️ PRIMARY USE CASE
This skill manages operational aspects of Confluence integration. Use for:
- Inspecting and clearing the cache directory
- Diagnosing API connectivity issues
- Troubleshooting rate limits
Cache reality check: current
confluence-asreleases never write response data to the cache directory (~/.confluence-skills/cache). Thecache-*commands manage/inspect that directory, but it stays empty unless something else populates it:cache-warmissues API requests and discards the responses (cache-statusstill shows 0 entries afterwards), and each CLI invocation builds a fresh HTTP session, so warming does not speed anything up.CONFLUENCE_CACHE_ENABLEDonly changes the Enabled/Disabled label incache-statusoutput.
When to Use / When NOT to Use
| Use This Skill | Use Instead |
|---|---|
| Check cache status | - |
| Clear/warm cache | - |
| Diagnose API issues | - |
| Check rate limits | - |
| Manage pages | confluence-page |
| Search content | confluence-search |
| Manage spaces | confluence-space |
Risk Levels
| Operation | Risk | Notes |
|---|---|---|
| Cache status | - | Read-only |
| API diagnostics | - | Read-only |
| Cache warm | - | Issues read-only API requests; does not add cache entries |
| Cache clear | ⚠️ | Deletes files from the cache directory |
When to Use This Skill
Use this skill when you need to:
- Inspect the cache directory: Check its size and entry counts by category
- Clear cache data: Remove stale or sensitive files from the cache directory
- Exercise read endpoints:
cache-warmfetches space metadata (useful as a connectivity smoke test; responses are not stored) - Diagnose API issues: Test connectivity and identify problems
- Check rate limits: Monitor API quota usage
Trigger conditions:
- Setting up new Confluence instance
- Troubleshooting 429 rate limit errors
- Cleaning up the cache directory (e.g. removing sensitive data left by older releases or other tools)
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.
- 3d ago First seen · 318 lines · 33 tokens per session scan A 61786125a1f3
confluence-ops is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (16 stars, last pushed today), licensed MIT. It adds 33 tokens to every session and 2,253 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-09-04.
Other skills, from other repositories
collection
Choose which SkillNote skill collection is active for this Codex project. Use when the user says "change collection", "switch skills", "use frontend skills", or "show collections".
audit-accomplishments
Use when preparing a performance self-reflection, midyear or annual review, promotion packet, or brag document; when asked to collect, mine, gather, or summarize your accomplishments, contributions, or impact over a period; or when assembling cited evidence of work done across GitHub, Jira, Notion, Slack, and local…
start-day
Use at the start of a workday or when the user says "start my day", "good morning", "/start-day", "morning", "what should I work on today", or wants a catch-up on what happened while they were away. Use when the user wants a short ranked list of what to tackle today.
tracking-time
Tracks time on tasks using timers or manual entries and generates timesheet reports in Astravue. Use when logging work hours, starting or stopping a timer, reviewing time entries, generating timesheets, or asking "how much time was spent on this?".
Daily brief / morning catch-up (Local MCP)
Use when the user asks "what's on my plate today", "catch me up", "morning brief", or wants a summary of their day across calendar, reminders and email. The single most common multi-step automation. Powered by Local MCP.
Inbox to action — triage, reply & schedule (Local MCP)
Use when the user wants to deal with their inbox — find what needs a response, draft replies, and turn emails into calendar events or reminders. Captures the common email→read→reply→schedule workflow. Powered by Local MCP.