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 ulises-jeremias/agent-toolkit --skill confluence-commentgit clone --depth 1 https://github.com/ulises-jeremias/agent-toolkitWrote 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-comment)<a href="https://agentmods.dev/skills/ulises-jeremias/agent-toolkit/confluence-comment"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/confluence-comment/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/ulises-jeremias/agent-toolkit/confluence-comment"><img src="https://agentmods.dev/badge/skills/ulises-jeremias/agent-toolkit/confluence-comment.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 3 findings, up to high
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 →
- high Tool Misuse · line 246 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
- medium Excessive Agency · line 160 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 224 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00034 | $0.01970 |
| Opus 5.5 | $0.00014 | $0.00788 |
| Sonnet 5.5 | $0.00007 | $0.00394 |
| Haiku 4.5 | $0.00003 | $0.00197 |
Grade A, and why
confluence-comment 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 20d 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 — 266 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Confluence Comment Skill
⚠️ PRIMARY USE CASE
This skill manages comments on Confluence pages. Use for:
- Adding footer comments (end of page)
- Adding inline comments (within content)
- Replying to existing comments
- Resolving/unresolving footer comments (inline comments are not supported by
resolve)
When to Use / When NOT to Use
| Use This Skill | Use Instead |
|---|---|
| Add/edit comments | - |
| Reply to comments | - |
| Resolve footer comments | - |
| Edit page content | confluence-page |
| Search comments | confluence-search |
Risk Levels
| Operation | Risk | Notes |
|---|---|---|
| List comments | - | Read-only |
| Add comment | - | Can be deleted |
| Update comment | ⚠️ | Overwrites original |
| Delete comment | ⚠️ | No recovery |
Overview
This skill provides comprehensive comment management for Confluence pages, supporting both footer comments and inline comments. Use it to add feedback, manage discussions, and track comment resolution.
CLI Commands
Output format tip: A global -o/--output flag placed before the subcommand (e.g. confluence-as -o json comment list 12345) sets the default output format for all subcommands; an explicit subcommand-level --output wins.
confluence-as comment add
Add a footer comment to a Confluence page.
Usage:
confluence-as comment add PAGE_ID "Comment text"
confluence-as comment add PAGE_ID --file comment.txt
Arguments:
page_id- Page ID to add comment tobody- Comment body text (optional if using --file)
Options:
--file,-f- Read comment body from file (alternative to body argument)--output,-o- Output format (text or json)
Note: Either body argument or --file option is required, but not both.
confluence-as comment list
Retrieve footer comments on a Confluence page. Returns at most --limit comments (default: 25, max: 250) and silently truncates at that limit - pass a higher --limit on pages with many comments.
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.
- 20d ago Changed bcef9d905207
- 2mo ago First seen · 266 lines · 34 tokens per session scan A 654b21ce9a35
confluence-comment is a skill published in the GitHub repository ulises-jeremias/agent-toolkit (19 stars, last pushed today), licensed MIT. It adds 34 tokens to every session and 1,970 once invoked, about $0.0001 per session on Opus 5.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.
confluence-comment compared with skills from other repositories
| Mod | Type | Stars | Last push | Licence | Scan | Tokens | Works with |
|---|---|---|---|---|---|---|---|
| confluence-commentulises-jeremias/agent-toolkit | Skill | 19 | today | MIT | A | 34 | Claude Code |
| collectionluna-prompts/skillnote | Skill | 68 | 4d ago | MIT | A | 39 | Codex |
| audit-accomplishmentspaultyng/skill-issue | Skill | 8 | 20d ago | MIT | A | 78 | Claude Code |
| start-daypaultyng/skill-issue | Skill | 8 | 20d ago | MIT | A | 69 | Claude Code, Codex |
| tracking-timeAstravueOrg/astravue-mcp-server | Skill | 12 | 2mo ago | Apache-2.0 | A | 53 | Claude Code |
| microsoft-outlookAceDataCloud/Skills | Skill | 17 | today | none | A | 68 | Claude Code |
| google-calendarAceDataCloud/Skills | Skill | 17 | today | none | A | 61 | Claude Code |