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 commands/talayash/agentrium/publishgit clone --depth 1 https://github.com/talayash/agentriumWhat 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.00887 |
| Opus 5 | $0.00000 | $0.00443 |
| Sonnet 5 | $0.00000 | $0.00177 |
| Haiku 4.5 | $0.00000 | $0.00089 |
Grade A, and why
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 2d 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 — 103 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Publish a new release of ClaudeTerminal
You are performing a full release of ClaudeTerminal. Follow every step below in order. Stop and ask the user if anything is ambiguous or fails.
Arguments
$ARGUMENTS - The new version number (e.g. 1.6.0). If not provided, ask the user what version to publish.
Step 1: Validate
- Confirm the version number with the user before proceeding.
- Read the current version from
package.jsonand verify the new version is higher. - Ensure the working tree is clean (
git status). If there are uncommitted changes, warn the user and ask whether to proceed or abort. - Ensure you are on the
masterbranch. If not, warn the user.
Step 2: Bump version in all files
Update the version string in all five of these files (replace the old version with the new one):
package.json- the"version"fieldsrc-tauri/Cargo.toml- theversionfield under[package]src-tauri/tauri.conf.json- the"version"fieldREADME.md- update these version references (link text AND URL for each row of the Download table):- The version badge:
version-X.Y.Z-green - Windows NSIS:
Agentrium_X.Y.Z_x64-setup.exe - Windows MSI:
Agentrium_X.Y.Z_x64_en-US.msi - macOS Apple Silicon:
Agentrium_X.Y.Z_aarch64.dmg - macOS Intel:
Agentrium_X.Y.Z_x64.dmg - Every row must be a real
[filename](https://github.com/talayash/agentrium/releases/latest/download/filename)link, not a bare backtick code span.
- The version badge:
CLAUDE.md- theCurrent version: **X.Y.Z**line
After editing, verify each file was updated correctly by reading the changed lines.
Step 2b: Add changelog entry
Add a new entry at the top of the src/changelog.json array for this version. Ask the user for a summary of the features/changes to include. Each entry has this format:
{
"version": "X.Y.Z",
"date": "YYYY-MM-DD",
"features": [
{ "title": "Feature name", "description": "Optional description" }
]
}
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.
- 2d ago First seen · 103 lines · 0 tokens per session scan A 9a974fe00e58
publish is a command published in the GitHub repository talayash/agentrium (39 stars, last pushed 2d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 887 tokens. 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-30.
Other commands, from other repositories
release
(dev-only) release maintainer harness — MoAI-ADK production release (Enhanced GitHub Flow, scripts/release.sh + GoReleaser). NOT distributed to user projects.
celebrate
You are celebrating a project milestone! Follow these steps to create a new release.
bump
Bump Claudepot version numbers in lock-step across Cargo.toml, Cargo.lock, package.json, src-tauri/tauri.conf.json, README.md, the web install page, and stub a CHANGELOG section. Runs a quality gate first. Does not commit — leaves changes for review, and documents the tag/push path that follows.
release
Создать релиз фреймворка Claude Code Starter.
review-renovate
Review and merge renovate PRs with automerge configuration updates.
spec-design
Create comprehensive technical design for a specification.