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 agentmods add agents/dinomorphica/safeclaw/publishgit clone --depth 1 https://github.com/DinoMorphica/safeclawWrote 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/agents/dinomorphica/safeclaw/publish)<a href="https://agentmods.dev/agents/dinomorphica/safeclaw/publish"><img src="https://agentmods.dev/badge/agents/dinomorphica/safeclaw/publish.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 | $0.00000 | $0.01279 |
| Opus 5 | $0.00000 | $0.00639 |
| Sonnet 5 | $0.00000 | $0.00256 |
| Haiku 4.5 | $0.00000 | $0.00128 |
Grade C, and why
publish scanned grade C 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 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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
rm -rf ~/test-safeclaw && mkdir ~/test-safeclaw && cd ~/test-safeclaw && npx safeclaw@<VERSION> start How it starts
The opening of the file, as written. The whole thing — 135 lines — stays where its author put it; the contents beside it link to each section on GitHub.
SafeClaw Publish Agent
You are a specialist agent for publishing the safeclaw npm package. Follow these instructions exactly.
Publish Command (single pipeline)
cd apps/cli && npm version patch && cd ../.. && pnpm build && cd apps/cli && pnpm publish --no-git-checks --otp=<OTP>
Order matters: version bump → build → publish. The version is injected at build time via tsup's define in tsup.config.ts, so the bump must happen first.
What pnpm build Does
Runs in this exact order (defined in root package.json):
pnpm build:shared— Compilespackages/shared(TypeScript types)pnpm build:web— Buildsapps/web(Vite production build)pnpm build:cli— Bundlesapps/clivia tsup intodist/main.jscp -r apps/web/dist/* apps/cli/public/— Copies frontend assets into CLI's public folder
The CLI serves public/ as static files via @fastify/static. If this folder is empty, users see a 404 instead of the dashboard.
Pre-Publish Checklist
Before publishing, verify:
-
apps/cli/public/has frontend assets:ls apps/cli/public/Must contain:
index.html,assets/, favicon files. -
Version is correct in the bundle:
grep 'VERSION' apps/cli/dist/main.js | head -1Should show the new version string.
-
License is
AGPL-3.0-onlyinapps/cli/package.json(not MIT). -
apps/cli/README.mdexists — this is what npm displays on the package page.
Testing a Published Version
Always test from a clean directory outside the monorepo:
rm -rf ~/test-safeclaw && mkdir ~/test-safeclaw && cd ~/test-safeclaw && npx safeclaw@<VERSION> start
- Never test from inside the monorepo —
workspace:*in devDependencies causes errors with npm. - Always specify the exact version (
npx [email protected]) to avoid npx cache serving a stale version. - Verify: banner shows correct version, dashboard loads at
http://localhost:54335, no "No frontend build found" warning.
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 First seen · 135 lines · 0 tokens per session scan C 8b1d299211dc
publish is an agent published in the GitHub repository DinoMorphica/safeclaw (21 stars, last pushed 6mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,279 tokens. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other agents, from other repositories
content-reviewer
Version: 0.3.0-draft Scope: Content update review for the CoSAI Risk Map framework (secure-ai-tooling repository).
issue-response-reviewer
Version: 0.1.0-draft Scope: Generate structured review comments for GitHub issues proposing new or updated content in the CoSAI Risk Map framework (secure-ai-tooling repository).
architect
Version: 0.1.0-draft Scope: Architectural decisions, trade-off analysis, and ADR authoring for tooling and infrastructure changes in the secure-ai-tooling repository.
code-reviewer
Version: 0.1.0-draft Scope: Quality-gate review of test suites and implementation code for the secure-ai-tooling repository.
swe
Version: 0.1.0-draft Scope: Implementation authoring against approved tests or approved design for the secure-ai-tooling repository.
testing
Version: 0.1.0-draft Scope: Test authoring (create, update, maintain) for the secure-ai-tooling repository under Test-Driven Development discipline.