Borrowing it
Nothing to install: this file belongs to dep/agent-rules. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/dep/agent-rules/main/.agents/skills/atlassian/SKILL.mdgit clone --depth 1 https://github.com/dep/agent-rulesWrote 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/dep/agent-rules/atlassian)<a href="https://agentmods.dev/skills/dep/agent-rules/atlassian"><img src="https://agentmods.dev/badge/skills/dep/agent-rules/atlassian/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/dep/agent-rules/atlassian"><img src="https://agentmods.dev/badge/skills/dep/agent-rules/atlassian.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.00033 | $0.00731 |
| Opus 5.5 | $0.00013 | $0.00292 |
| Sonnet 5.5 | $0.00007 | $0.00146 |
| Haiku 4.5 | $0.00003 | $0.00073 |
Grade A, and why
acli 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 1mo 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 — 120 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atlassian Skill using acli (Command Line Interface)
Overview
Utilize Atlassian Command Line Interface (CLI) to effortlessly engage with our suite of products through a streamlined command-line interface. Atlassian CLI provides a powerful toolset that allows users to automate tasks, integrate processes, and interact with various Atlassian products such as Jira, all from the comfort of your terminal.
Options
acli --help
Getting Started
Check to see if acli is installed:
acli --version
It not installed, install it:
brew tap atlassian/homebrew-acli
brew install acli
It installed, verify it:
acli --version
Authenticating to Jira
To connect to your Atlassian account, you need to authenticate.
Check if you are already authenticated:
acli jira auth status
If you are not authenticated, authenticate:
acli jira auth login --web
acli Jira Commands
Create a work item
acli jira workitem create
# Create work item by supplying a summary, project name and work item type
acli jira workitem create --summary "New Task" --project "TEAM" --type "Task"
# Create work item from file and supplying all work item details
acli jira workitem create --from-file "workitem.txt" --project "PROJ" --type "Bug" --assignee "[email protected]" --label "bug,cli"
# Generate a JSON file that could be used for workitem creation via --from-json flag
acli jira workitem create --generate-json
# Create work item from a JSON file
acli jira workitem create --from-json "workitem.json"
View a work item
acli jira workitem view
Edit a work item
acli jira workitem edit
acli jira workitem edit
# Edit work item with work item keys
acli jira workitem edit --key "KEY-1,KEY-2" --summary "New Summary"
# Edit work item with JQL query
acli jira workitem edit --jql "project = TEAM" --assignee "[email protected]"
# Edit work item with Filter ID
acli jira workitem edit --filter 10001 --description "Updated description" --yes
# Generate a JSON file that could be used for workitem edit via --from-json flag
acli jira workitem edit --generate-json
# Edit work item from a JSON file
acli jira workitem edit --from-json "workitem.json"
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.
- 1mo ago First seen · 120 lines · 33 tokens per session scan A c4480f057c43
acli is a skill published in the GitHub repository dep/agent-rules (11 stars, last pushed 4mo ago), licensed MIT. It adds 33 tokens to every session and 731 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-08-30.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…