Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/ShreyPaharia/octomuxnpx agentmods add skills/shreypaharia/octomux/implementWrote 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/shreypaharia/octomux/implement)<a href="https://agentmods.dev/skills/shreypaharia/octomux/implement"><img src="https://agentmods.dev/badge/skills/shreypaharia/octomux/implement/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/shreypaharia/octomux/implement"><img src="https://agentmods.dev/badge/skills/shreypaharia/octomux/implement.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.01500 |
| Opus 5 | $0.00016 | $0.00750 |
| Sonnet 5 | $0.00007 | $0.00300 |
| Haiku 4.5 | $0.00003 | $0.00150 |
Grade A, and why
implement 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 9d 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 — 191 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Implement a Jira Ticket
Fetch a Jira ticket, check for an existing plan, set up a branch, and implement with lint+test verification before committing.
Announce at start: "Implementing : "
Checklist
- Fetch ticket — get Jira ticket details and any existing plan
- Assess readiness — is this ready to implement, or does it need
/planfirst? - Set up branch — create worktree or branch
- Read project conventions — CLAUDE.md, learnings, relevant package docs
- Implement — follow the plan or work from the ticket description
- Verify —
make lint && make test(or project equivalent) - Commit — conventional commit referencing the ticket
- Report — summary with next steps (PR creation)
Jira Authentication
Before any Jira call, test connectivity by calling getAccessibleAtlassianResources(). If it fails or returns an auth error, stop and prompt the user:
"Jira is not authenticated. Please run
/pluginand authenticate the Atlassian plugin, then try again."
Do not proceed with Jira operations until auth is confirmed.
Phase 1: Fetch Ticket
Extract the ticket key from the argument (e.g., IN-945 from /implement IN-945 or from a URL).
1a. Get Jira details (also serves as auth check):
getAccessibleAtlassianResources() -> cloudId (if this fails, follow Jira Authentication section)
getJiraIssue(cloudId, issueKey, fields=["summary","description","priority","labels","status","parent"], responseContentFormat="markdown")
1b. Check for existing local plan (parallel):
ls docs/plans/<ticket-key>-*.md 2>/dev/null
If a plan file exists, read it — this is the primary implementation guide.
If no plan file exists, use the ticket description's Approach section as the guide.
Phase 2: Assess Readiness
Check if the ticket has enough detail to implement:
- Ready: Has clear What/Why/Approach or an existing plan file -> proceed
- Needs planning: Description is vague, scope is unclear, or estimate was XL -> recommend
/plan <ticket-key>first
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.
- 9d ago First seen · 191 lines · 33 tokens per session scan A fa3d241890b1
implement is a skill published in the GitHub repository ShreyPaharia/octomux (22 stars, last pushed 7d ago), licensed MIT. It adds 33 tokens to every session and 1,500 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-08-30.
Other skills, from other repositories
muster
Coordinate with other coding-agent sessions — any machine, any vendor — on this repo via the muster CLI. Use when the user says /muster, asks to join or check a fleet, mentions muster, or wants to coordinate work with other sessions/machines on this repo.
repo-guidance
Navigate the Composio SDK monorepo, branch and PR workflow, repo layout, generated-file boundaries, changesets, and shared maintenance rules. Use when work spans multiple packages, when deciding where code belongs, when preparing a PR, or when the user asks about repository conventions rather than a specific SDK…
python-release
Handle Python SDK release, build, bump, packaging metadata, PyPI client pin, uv.lock, nox/build workflow, and publish verification changes. Use for Python release process work or dependency pin bumps; do not use for ordinary Python feature implementation.
checkpoint-management
Git-backed state management for safe rollback. Create and restore checkpoints with tagged commits and metadata tracking.
contributor
End-to-end open source contribution workflow: from scanning issues to submitting PRs. Use this skill whenever the user wants to contribute to an open source project, find issues to fix, submit a pull request, fork a repo to contribute, fix a GitHub issue, or mentions 'open source contribution'. Also trigger when they…
git-commit-smart
Generates meaningful, conventional commit messages automatically. Use when committing code changes. Analyzes diff to create descriptive commits following best practices.