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 commands/thelobbi/claude/atlassian-syncgit clone --depth 1 https://github.com/TheLobbi/claudeWrote 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/commands/thelobbi/claude/atlassian-sync)<a href="https://agentmods.dev/commands/thelobbi/claude/atlassian-sync"><img src="https://agentmods.dev/badge/commands/thelobbi/claude/atlassian-sync.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.00000 | $0.02363 |
| Opus 5 | $0.00000 | $0.01182 |
| Sonnet 5 | $0.00000 | $0.00473 |
| Haiku 4.5 | $0.00000 | $0.00236 |
Grade A, and why
atlassian-sync scanned grade A with 1 finding 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -X POST "$JIRA_URL/rest/api/3/issue" \ How it starts
The opening of the file, as written. The whole thing — 243 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Atlassian Sync
Synchronize data between GitHub, Jira, and Confluence.
Instructions
Execute the following workflows to sync Atlassian tools:
1. GitHub Issue to Jira
```bash export JIRA_URL="${JIRA_URL:-https://your-domain.atlassian.net}" export JIRA_AUTH=$(echo -n "$JIRA_EMAIL:$JIRA_API_TOKEN" | base64)
Parse GitHub issue (if using gh CLI)
GH_ISSUE=$(gh issue view 123 --json title,body,labels,assignees) TITLE=$(echo $GH_ISSUE | jq -r '.title') BODY=$(echo $GH_ISSUE | jq -r '.body') LABELS=$(echo $GH_ISSUE | jq -r '[.labels[].name] | join(",")')
Create corresponding Jira issue
curl -X POST "$JIRA_URL/rest/api/3/issue"
-H "Authorization: Basic $JIRA_AUTH"
-H "Content-Type: application/json"
-d "{
"fields": {
"project": {"key": "GA"},
"issuetype": {"name": "Task"},
"summary": "[GitHub #123] $TITLE",
"description": {
"type": "doc",
"version": 1,
"content": [{"type": "paragraph", "content": [{"type": "text", "text": "$BODY"}]}]
},
"labels": ["github-sync", "gh-123"]
}
}"
```
2. Jira Issue to GitHub
```bash
Get Jira issue
JIRA_ISSUE=$(curl -s -X GET "$JIRA_URL/rest/api/3/issue/GA-123"
-H "Authorization: Basic $JIRA_AUTH")
SUMMARY=$(echo $JIRA_ISSUE | jq -r '.fields.summary')
DESCRIPTION=$(echo $JIRA_ISSUE | jq -r '.fields.description.content[0].content[0].text // "No description"')
Create GitHub issue
gh issue create
--title "[GA-123] $SUMMARY"
--body "$DESCRIPTION
Jira Link: $JIRA_URL/browse/GA-123"
--label "jira-sync"
```
3. PR to Jira Comment
```bash
Extract Jira key from PR title or branch
PR_TITLE=$(gh pr view 456 --json title -q '.title') JIRA_KEY=$(echo "$PR_TITLE" | grep -oE 'GA-[0-9]+')
if [ -n "$JIRA_KEY" ]; then PR_URL=$(gh pr view 456 --json url -q '.url') PR_STATUS=$(gh pr view 456 --json state -q '.state')
Add comment to Jira
curl -X POST "$JIRA_URL/rest/api/3/issue/$JIRA_KEY/comment"
-H "Authorization: Basic $JIRA_AUTH"
-H "Content-Type: application/json"
-d "{
"body": {
"type": "doc",
"version": 1,
"content": [{
"type": "paragraph",
"content": [
{"type": "text", "text": "GitHub PR #456: $PR_STATUS\n"},
{"type": "text", "text": "$PR_URL", "marks": [{"type": "link", "attrs": {"href": "$PR_URL"}}]}
]
}]
}
}"
fi
```
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 · 243 lines · 0 tokens per session scan A cd27577ee67b
atlassian-sync is a command published in the GitHub repository TheLobbi/claude (21 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 2,363 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other commands, from other repositories
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.
analyze
Perform a non-destructive cross-artifact consistency and quality analysis across spec.md, plan.md, and tasks.md after task generation.