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 juxt/claude-plugins --skill a-stargit clone --depth 1 https://github.com/juxt/claude-pluginsWrote 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/juxt/claude-plugins/a-star)<a href="https://agentmods.dev/skills/juxt/claude-plugins/a-star"><img src="https://agentmods.dev/badge/skills/juxt/claude-plugins/a-star/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/juxt/claude-plugins/a-star"><img src="https://agentmods.dev/badge/skills/juxt/claude-plugins/a-star.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.00121 | $0.01113 |
| Opus 5.5 | $0.00048 | $0.00445 |
| Sonnet 5.5 | $0.00024 | $0.00223 |
| Haiku 4.5 | $0.00012 | $0.00111 |
Grade A, and why
a-star 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 3d 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
a-star
Interpret MUST, MUST NOT, SHOULD, SHOULD NOT, MAY, etc. per RFC 2119.
- Dart to an end-to-end as quickly as possible.
- Use what the dart found to land atomic, comprehensible, correct, compliant changes. Go to 1 as required.
Throwing a drive away is always an option: revert it, mark its sub-goal not done, and dart again with what it taught.
A drive that fails before it lands steps back per a-star:drive.
Roles
- You, the main session, are the super agent. You triage what darts raise, and write everything that lands, including the tests.
- The dart agent reaches the goal end-to-end and reports. Its code never lands.
A user's question is a question, not a go-ahead. "Is that a good idea?" wants an answer; an offer of the next step waits for a yes.
Sub-goals
- Sub-goals come from darts, not from reading the code.
- A sub-goal is one tidy or one advance, landed by a drive.
- Each commit is one atomic unit of change, its own tests and docs included. The user reviews a branch commit by commit, understanding and agreeing with each before the next; a commit whose tests or docs arrive later can't be agreed with on its own.
- Together, a card's sub-goals MUST complete it.
- The landed code keeps the data structures a dart got right, and leaves out what it built around the ones it didn't.
A structure change and a behaviour change never share a commit: a tidy changes structure, an advance changes behaviour, and a-star:drive lands either.
What to record
In whatever the session tracks its work with:
- a sub-goal, and what it depends on;
- a decision — a call you aren't sure of is an open question instead;
- an open question, and what it blocks;
- a sub-goal done, with its commits;
- what's in hand — the sub-goal being worked, and anything that interrupted it;
- whether the user is watching (
a-star:primary,a-star:secondary). A session starts primary, unless nobody can watch it — headless, cloud or scheduled — when it starts secondary.
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.
- 3d ago Changed · +4 lines 865fa8bd4206
- 4d ago Changed 9ec38d36adb8
- 7d ago Changed · -2 tokens per session b83c8a1690e2
- 11d ago Changed · -90 lines · +8 tokens per session f3228027ba44
- 13d ago First seen · 169 lines · 115 tokens per session scan A 5bbc330ee349
a-star is a skill published in the GitHub repository juxt/claude-plugins (10 stars, last pushed yesterday), licensed MIT. It adds 121 tokens to every session and 1,113 once invoked, about $0.0005 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-10-04.
Other skills, from other repositories
prowler-commit
Creates professional git commits following conventional-commits format. Trigger: When creating commits, after completing code changes, when user asks to commit.
gh-auth-isolation
Safely manage multiple GitHub identities (EMU + personal) in agent workflows.
comet-github
A routing guide for Comet-related GitHub work. It directs requests about pull requests, issues, CI failures, ideas, and fixes to the appropriate review or implementation process.
release-helper
Ensures configuration and code changes are released correctly. Use PROACTIVELY whenever you edit config.json, change any setting, or fix a configuration bug in this project, so the change reaches production.
github-skill
Work with GitHub via the gh CLI — clone repositories, create/list/merge pull requests, create/list issues, and run any other gh command (API calls, workflow runs, releases, repo administration). List operations return parsed JSON.
re0-merge
Review and land an external contribution the way this suite does: gate it against the thesis, land it with the author's credit intact, complete a new skill rather than merging it raw, then approve, credit, and explain before closing. Use when reviewing a pull request, as any collaborator or maintainer, not only the…