Borrowing it
Nothing to install: this file belongs to talayash/agentrium. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/talayash/agentrium/master/.claude/agents/ipc-checker.mdgit clone --depth 1 https://github.com/talayash/agentriumWrote 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/talayash/agentrium/ipc-checker)<a href="https://agentmods.dev/agents/talayash/agentrium/ipc-checker"><img src="https://agentmods.dev/badge/agents/talayash/agentrium/ipc-checker/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/agents/talayash/agentrium/ipc-checker"><img src="https://agentmods.dev/badge/agents/talayash/agentrium/ipc-checker.svg" alt="Reviewed on agentmods" width="80" 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.00000 | $0.00369 |
| Opus 5.5 | $0.00000 | $0.00148 |
| Sonnet 5.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 1mo 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 Agentrium 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.
- 1mo ago Changed 391dfc488b2e
- 1mo ago First seen · 37 lines · 0 tokens per session scan A 3b6091101d80
ipc-checker is an agent published in the GitHub repository talayash/agentrium (46 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
python-developer
Write clean, efficient Python code following PEP standards. Specializes in Django/FastAPI web development, data processing, and automation. Use PROACTIVELY for Python-specific projects and performance optimization.
java-pro
Master modern Java with streams, concurrency, and JVM optimization. Handles Spring Boot, reactive programming, and enterprise patterns. Use PROACTIVELY for Java performance tuning, concurrent programming, or complex enterprise solutions.
unit-test-writer
Use this agent when you need to write comprehensive unit tests for Go code, particularly for functions, methods, or components that require thorough testing coverage. Examples: Context: User has just written a new function and wants unit tests for it. user: 'I just wrote this function to validate email addresses, can…
php-expert
Use when: composer.json present WITHOUT an artisan file. Do NOT use for: Laravel apps (composer.json + artisan → laravel-expert), frontend (framework experts).
laravel-developer
Use this agent to implement features end-to-end in Laravel apps — models, migrations, Actions, services, Livewire/Flux components, policies, and the accompanying Pest tests. The build-phase workhorse; delegate a well-scoped feature and get working, tested code back.
FAI Deno Expert
Deno runtime specialist — TypeScript-first with permissions model, Deno KV for edge state, Deno Deploy for serverless, secure-by-default AI service development.