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.
git clone --depth 1 https://github.com/GodsB1025/justoneWrote 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/godsb1025/justone/justone-publish)<a href="https://agentmods.dev/commands/godsb1025/justone/justone-publish"><img src="https://agentmods.dev/badge/commands/godsb1025/justone/justone-publish/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/commands/godsb1025/justone/justone-publish"><img src="https://agentmods.dev/badge/commands/godsb1025/justone/justone-publish.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.00022 | $0.00768 |
| Opus 5.5 | $0.00009 | $0.00307 |
| Sonnet 5.5 | $0.00004 | $0.00154 |
| Haiku 4.5 | $0.00002 | $0.00077 |
Grade A, and why
justone-publish 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 — 47 lines — stays where its author put it; the contents beside it link to each section on GitHub.
The user has invoked /justone-publish. This pushes their just-built project to GitHub and registers it on the JustOne gallery.
Required steps, in order
- Load the contract. Read
~/.claude/skills/justone/SKILL.mdif you haven't already this session. - Pre-flight + manifest check. Run:
Stop on any failure and report the cause to the user (e.g. missing manifest, missing gh auth, missing token).node ~/.claude/skills/justone/scripts/verify-environment.mjs --check-manifest - Write a sane
.gitignoreif one doesn't exist. Cover:node_modules,dist,.next,.vercel,.env,.env.*,*.log,.DS_Store,Thumbs.db, secrets like*.pem,*.key,id_rsa*. - Initialize git + create the public repo + push. Pick a slug-friendly repo name based on
manifest.title(e.g.justone-alarm-app). If that name already exists on the user's GitHub, append a short random suffix.
Ifgit init -q git add . git commit -q -m "Create with /justone" gh repo create <repo-name> --public --source=. --pushgh repo createfails for name collision, retry with a-xxxxsuffix. - (Optional) Generate
justone/thumbnail.png. For v0.1 this is best-effort — if the project is web and trivial to start, you may runnpm install && npm run devbriefly and use Playwright to screenshotlocalhost:<port>. Otherwise skip and the gallery will use a manifest-based card. Don't block publish on this. - Update the manifest if a thumbnail was generated. Set
thumbnailPathorscreenshotPathaccordingly, thengit add+git commit -m "Add thumbnail"+git push. - Upload to the gallery. Run:
This readsnode ~/.claude/skills/justone/scripts/upload-submission.mjs~/.justone/credentials(thejo_pat_*token) and POSTs to the gallery. If the response is200/201with a gallery URL, you're done. - Report the result to the user. Show the gallery URL prominently:
✓ Published. View at: https://justone-app.vercel.app/s/your-slug
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 · 47 lines · 22 tokens per session scan A 942161818542
justone-publish is a command published in the GitHub repository GodsB1025/justone (2 stars, last pushed 5mo ago), licensed MIT. It adds 22 tokens to every session and 768 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-31.
Other commands, from other repositories
update-infos-release
Update Claude Code releases tracking (guide + landing + version bump).
release
Release guide version (CHANGELOG + VERSION + README + landing sync + commit + push).
changelog
Generate a changelog entry from git commits since the last tag using conventional commit format.
changelog
View recent CHANGELOG entries.
ship
Branch, commit, open PR, gather Claude + every enabled AI reviewer (Copilot, CodeRabbit, etc.), fix/justify/resolve every finding, loop until clean, then merge. Run only when implementation is finished AND the owner has said to ship (e.g. "ship it") — never self-invoke just because the work looks done. To design and…
release
Cut a semver release for the current repo — bump computed from conventional commits, evidence preview, tag + GitHub release.