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/add-commandgit 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.00296 |
| Opus 5 | $0.00000 | $0.00148 |
| Sonnet 5 | $0.00000 | $0.00059 |
| Haiku 4.5 | $0.00000 | $0.00030 |
Grade A, and why
add-command 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 yesterday.
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.
What it actually says
Add a new Tauri IPC command
Add a new Tauri IPC command named $ARGUMENTS. If the name is not provided, ask the user.
Follow these steps in order:
Step 1: Understand the command
Ask the user (if not already clear) what the command should do, what parameters it takes, and what it returns.
Step 2: Add the Rust handler
Add an async handler function in src-tauri/src/commands.rs. Follow existing patterns:
- Use
#[tauri::command]attribute - Accept
state: tauri::State<'_, AppState>if database or terminal access is needed - Return
Result<T, String>where T is the appropriate return type - Map errors with
.map_err(|e| e.to_string())
Step 3: Register in main.rs
Add the new command to the invoke_handler macro call in src-tauri/src/main.rs.
Step 4: Add the TypeScript invoke call
Add the corresponding invoke<ReturnType>('command_name', { params }) call in the appropriate frontend file. Import invoke from @tauri-apps/api/core.
Step 5: Verify
- Confirm the command name matches exactly between Rust registration and TypeScript invoke
- Confirm parameter names match between Rust and TypeScript
- Confirm the return type is handled properly (try/catch in TypeScript)
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.
- yesterday First seen · 32 lines · 0 tokens per session scan A 47fd97191518
add-command is a command published in the GitHub repository talayash/agentrium (39 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 296 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
spec-design
Create comprehensive technical design for a specification.
vibe-agents
Step 4 of the vibe-coding workflow: generate AGENTS.md + tool configs so the AI builder stays on track.
validate-gap
Analyze implementation gap between requirements and existing codebase.
spec-impl
Execute spec tasks using TDD methodology.
oss-docs
(user-owned) oss-docs harness — README 4-locale + docs-site publishing for the moai-adk-go OSS project (adk.mo.ai.kr, Vercel auto-deploy).
fix
Auto-detect and fix LSP errors, linting issues, and type errors.