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 justnau1020/claude-os --skill deploygit clone --depth 1 https://github.com/justnau1020/claude-osWrote 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/justnau1020/claude-os/deploy)<a href="https://agentmods.dev/skills/justnau1020/claude-os/deploy"><img src="https://agentmods.dev/badge/skills/justnau1020/claude-os/deploy.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.1 | $0.00024 | $0.00433 |
| Opus 5 | $0.00012 | $0.00217 |
| Sonnet 5 | $0.00005 | $0.00087 |
| Haiku 4.5 | $0.00002 | $0.00043 |
Grade A, and why
deploy 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 8d 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.
allowed-tools: Bash(git *), Bash(gh *), Bash(curl *), Bash(pytest *), Bash(ruff *), Bash(mypy *), Bash(npm *) What it actually says
Deploy to Production
WARNING: This deploys to the live production environment.
Pre-Deploy Checklist
Before pushing, verify ALL of these pass:
- Tests pass: Run the full test suite
- Lint clean: Run the project's linter with no errors
- Types clean: Run the type checker with no errors (if applicable)
- On deploy branch:
git branch --show-currentmust be the deploy branch (usuallymain) - Working tree clean:
git statusshows no uncommitted changes - Up to date:
git pull origin mainhas no conflicts
If ANY check fails, stop and report the issue. Do NOT proceed with deployment.
Deploy
Push to the deploy branch to trigger the CI/CD pipeline:
git push origin main
Monitor
- Watch CI:
gh run list --limit 1-- wait for the run to complete - Check run status:
gh run view <run-id>-- verify all jobs pass - Health check: After CI completes, wait 60 seconds then:
curl -sf https://{PRODUCTION_URL}/health - Expected healthy response includes a status field indicating the service is running
If Deployment Fails
- Check CI logs:
gh run view <run-id> --log-failed - If the app is down, refer to the project's runbook for rollback procedures
- Quick rollback: revert the commit and push again
Reference
Check the project's deploy/ directory or ops documentation for full operational procedures.
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.
- 8d ago First seen · 52 lines · 24 tokens per session scan A 195fca4ed295
deploy is a skill published in the GitHub repository justnau1020/claude-os (3 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 24 tokens to every session and 433 once invoked, about $0.0001 per session on Opus 5. 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 skills, from other repositories
changelog-gen
A changelog generator that turns Git history into a version-by-version record of project changes. A changelog is a readable summary of new features, fixes, breaking changes, documentation, and other updates.
changelog-rules
Shared changelog conventions and formatting rules referenced by /create-changelog and /update-changelog. Not typically invoked directly.
release-engineering
Plan and verify software releases with versioning, changelogs, release branches, feature flags, canaries, migration gates, rollback, deployment checks, and release readiness. Use when preparing a release, shipping a risky PR, coordinating app/backend/database rollout, recovering from a bad deploy, or defining release…
create-changelog
Create a CHANGELOG.md following keepachangelog.com conventions with version history backfilled from GitHub releases or git tags. Use when the user asks to "create a changelog", "add a changelog", "initialize changelog", "start a changelog", "set up changelog", "generate changelog", or "backfill changelog".
update-changelog
Update the Unreleased section of CHANGELOG.md based on current changes. No-op if CHANGELOG.md does not exist. Use when the user asks to "update changelog", "add to changelog", "update the changelog", "changelog entry", "add changelog entry", or "log this change".
ship
Verify and publish by pushing, opening a PR, and watching CI; land mode merges then cleans branches. Triggers "ship it", "create PR", "/ship", "watch the PR", "babysit CI"; land mode "land it", "/ship land", "fix CI and merge".