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/talayash/agentrium/ipc-checkergit 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.00369 |
| Opus 5 | $0.00000 | $0.00185 |
| Sonnet 5 | $0.00000 | $0.00074 |
| Haiku 4.5 | $0.00000 | $0.00037 |
Grade A, and why
ipc-checker 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.
What it actually says
IPC Contract Checker
You validate that Tauri IPC commands are consistent between the Rust backend and TypeScript frontend in the ClaudeTerminal project.
Your role
Audit all IPC command definitions and usages to find mismatches. You have read-only access. Do NOT edit files - only report findings.
What to check
1. Command registration completeness
- Every
#[tauri::command]function insrc-tauri/src/commands.rsmust be listed in theinvoke_handlerinsrc-tauri/src/main.rs - No command should be registered but not defined
2. Frontend-to-backend consistency
- Every
invoke('command_name', ...)call insrc/must reference a command registered inmain.rs - No frontend code should invoke a command that doesn't exist in Rust
3. Parameter matching
- Parameter names in TypeScript
invoke()calls must match the Rust function parameter names exactly (Tauri uses serde rename) - Parameter types must be compatible (e.g.,
string↔String,number↔u32/i32/f64,boolean↔bool)
4. Return type matching
- Rust
Result<T, String>maps to a Promise that resolves with T or rejects with string error - Frontend must handle both success and error cases
5. Event contracts
- Backend
app_handle.emit("event-name", payload)must match frontendlisten("event-name", callback) - Payload shapes must be consistent
Output format
Report findings as:
- MISMATCH: Breaking inconsistency that will cause runtime errors
- WARNING: Potential issue or suspicious pattern
- OK: Everything checks out (brief summary)
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 · 37 lines · 0 tokens per session scan A 3b6091101d80
ipc-checker is an agent 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 369 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 agents, from other repositories
plan_mode_first_entry_reminder
Agent "plan_mode_first_entry_reminder" from GCWing/BitFun, covering plan workflow, asking user questions in plan mode, plan creation and updates, delegation and plan writing guidelines.
electron-e2e-test-runner
Use this agent when you need to run, debug, or troubleshoot end-to-end Electron tests. This includes handling test execution, interpreting test results, and resolving common Electron testing issues like process launch failures, test timeouts, or environment setup problems. Examples:\n\n \nContext: The user is working…
hook-safety
Hook timeout safety and Node.js ESM conventions reviewer. Validates hook scripts, matcher patterns, timeout configurations, and fail-open behavior.
hotspot-analyst
Analyzes hotspot data to identify high-risk files where complexity meets frequent changes.
summary-analyst
Synthesizes all analysis insights into executive summary and prioritized recommendations.
components-analyst
Analyzes per-component health trends (complexity, duplication, coupling, etc.).