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 darshitpp/x-agent --skill juniegit clone --depth 1 https://github.com/darshitpp/x-agentWrote 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/darshitpp/x-agent/junie)<a href="https://agentmods.dev/skills/darshitpp/x-agent/junie"><img src="https://agentmods.dev/badge/skills/darshitpp/x-agent/junie/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/darshitpp/x-agent/junie"><img src="https://agentmods.dev/badge/skills/darshitpp/x-agent/junie.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.00075 | $0.00179 |
| Opus 5.5 | $0.00030 | $0.00072 |
| Sonnet 5.5 | $0.00015 | $0.00036 |
| Haiku 4.5 | $0.00007 | $0.00018 |
Grade A, and why
junie 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 21d 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.
What it actually says
Cross-Agent Task Runner — Junie CLI
Procedures
Step 1: Execute Shared Procedure
- Read
references/shared-procedure.mdfor the core workflow (mode inference, context gathering, prompt construction, result presentation). - Read
references/cli-junie.mdfor Junie-specific flags, model selection heuristics, and version compatibility matrix. - Follow the shared procedure using the Junie-specific details.
What ships with it
3 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.
- 21d ago Changed · -7 lines · -8 tokens per session 789e0394c2cb
- 1mo ago First seen · 28 lines · 83 tokens per session scan A 29e4499a1e46
junie is a skill published in the GitHub repository darshitpp/x-agent (2 stars, last pushed 21d ago), licensed MIT. It adds 75 tokens to every session and 179 once invoked, about $0.0003 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-31.
Other skills, from other repositories
testing-anti-patterns
Reviews test code to identify and fix common testing anti-patterns including flaky tests, over-mocking, brittle assertions, test interdependency, and hidden test logic. Flags bad patterns, explains the specific defect, and provides corrected implementations. Use when reviewing test code, debugging intermittent or…
structured-code-review
Performs a structured five-stage code review covering requirements compliance, correctness, code quality, testing, and security/performance. Each stage uses targeted checklists and categorized feedback (Blocker/Major/Minor/Nit) with actionable suggestions and rationale. Use when the user asks for code review, PR…
refactor
Restructures existing code without changing its behavior: maps callers and test coverage, adds characterization tests where coverage is thin, then applies the change in small steps verified against the full test suite after each one. Use when the user wants to refactor, extract a method or class, simplify logic…
review-code
Runs one adaptive multi-agent code review of a PR, commit, or the whole codebase. Always covers six core dimensions (correctness, performance, code style, test coverage, error handling, simplicity/over-engineering) plus architecture and design patterns, then adds security, dependency, deep-performance, and UI/motion…
review-perf
Deep-dive performance audit of database queries, algorithmic complexity, frontend bottlenecks, and resource leaks for a PR, a commit, or the whole codebase, producing a severity-ranked report. Use when the user explicitly wants a dedicated performance review, asks to "audit performance", "find N+1 queries", "check for…
find-simplifications
Use for a periodic repo-wide sweep of qwen-code for accumulated excess surface — dead components and files, orphaned locale keys, exports nothing consumes, added-then-removed scaffolding — filing candidates on a tracking issue and landing only what a maintainer has said yes to. Repo-wide and evidence-first; every…