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 bestagentkits/agency-skills --skill atlassian-templatesgit clone --depth 1 https://github.com/bestagentkits/agency-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/bestagentkits/agency-skills/atlassian-templates)<a href="https://agentmods.dev/skills/bestagentkits/agency-skills/atlassian-templates"><img src="https://agentmods.dev/badge/skills/bestagentkits/agency-skills/atlassian-templates/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/bestagentkits/agency-skills/atlassian-templates"><img src="https://agentmods.dev/badge/skills/bestagentkits/agency-skills/atlassian-templates.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.00062 | $0.02813 |
| Opus 5 | $0.00031 | $0.01406 |
| Sonnet 5 | $0.00012 | $0.00563 |
| Haiku 4.5 | $0.00006 | $0.00281 |
Grade A, and why
atlassian-templates 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 12d 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.
Copies of this mod
1 near-identical copy found in the catalogue:
- atlassian-templates — 100% identical, 2 lines differ
How it starts
The opening of the file, as written. The whole thing — 234 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atlassian Template & Files Creator Expert
Specialist in creating, modifying, and managing reusable templates and files for Jira and Confluence. Ensures consistency, accelerates content creation, and maintains org-wide standards.
Workflows
Template Creation Process
- Discover: Interview stakeholders to understand needs
- Analyze: Review existing content patterns
- Design: Create template structure and placeholders
- Implement: Build template with macros and formatting
- Test: Validate with sample data — confirm template renders correctly in preview before publishing
- Document: Create usage instructions
- Publish: Deploy to appropriate space/project via MCP (see MCP Operations below)
- Verify: Confirm deployment success; roll back to previous version if errors occur
- Train: Educate users on template usage
- Monitor: Track adoption and gather feedback
- Iterate: Refine based on usage
Template Modification Process
- Assess: Review change request and impact
- Version: Create new version, keep old available
- Modify: Update template structure/content
- Test: Validate changes don't break existing usage; preview updated template before publishing
- Migrate: Provide migration path for existing content
- Communicate: Announce changes to users
- Support: Assist users with migration
- Archive: Deprecate old version after transition; confirm deprecated template is unlisted, not deleted
Blueprint Development
- Define blueprint scope and purpose
- Design multi-page structure
- Create page templates for each section
- Configure page creation rules
- Add dynamic content (Jira queries, user data)
- Test blueprint creation flow end-to-end with a sample space
- Verify all macro references resolve correctly before deployment
- HANDOFF TO: Atlassian Admin for global deployment
Confluence Templates Library
See references/template-design-patterns.md for template design patterns and references/governance-framework.md for the governance model. For deployment-ready storage-format markup, use the bundled scaffolder (see Template scaffolder below). The following summarises the standard types this skill creates and maintains.
What ships with it
4 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 12d ago First seen · 234 lines · 62 tokens per session scan A bc2825d1377c
atlassian-templates is a skill published in the GitHub repository bestagentkits/agency-skills (11 stars, last pushed 2mo ago), licensed MIT. It adds 62 tokens to every session and 2,813 once invoked, about $0.0003 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
curate-collection
Build and maintain a library collection through acquisitions, weeding (deaccessioning), collection assessment, reader advisory, and interlibrary loan coordination. Covers selection criteria, collection development policies, the CREW/MUSTIE method for weeding, usage analysis, and responsive collection management. Use…
design-on-call-rotation
Design sustainable on-call rotations with balanced schedules, clear escalation policies, fatigue management, and handoff procedures. Minimize burnout while maintaining incident response coverage. Use when setting up on-call for the first time, scaling a team from 2-3 to 5+ engineers, addressing on-call burnout or…
design-training-program
Design a GxP training programme covering training needs analysis by role, curriculum design (regulatory awareness, system-specific, data integrity), competency assessment criteria, training record retention, and retraining triggers for SOP revisions and incidents. Use when a new validated system requires user training…
conduct-retrospective
Conduct a project or sprint retrospective by gathering data from status reports and velocity metrics, structuring what went well and what needs improvement, and generating actionable improvement items with owners and due dates. Use at the end of a sprint, after a project phase or milestone, following a significant…
create-github-issues
Structured GitHub issue creation from review findings or task breakdowns. Groups related findings into logical issues, applies labels, and produces issues with standard templates including summary, findings, and acceptance criteria. Designed to consume output from review-codebase or similar review skills.
create-work-breakdown-structure
Create a Work Breakdown Structure (WBS) and WBS Dictionary from project charter deliverables. Covers hierarchical decomposition, WBS coding, effort estimation, dependency identification, and critical path candidates. Use after a project charter is approved, when planning a classic or waterfall project with defined…