Borrowing it
Nothing to install: this file belongs to mylee04/code-notify. 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/mylee04/code-notify/main/.claude/agents/installation-tester.mdgit clone --depth 1 https://github.com/mylee04/code-notifyWrote 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/mylee04/code-notify/installation-tester)<a href="https://agentmods.dev/agents/mylee04/code-notify/installation-tester"><img src="https://agentmods.dev/badge/agents/mylee04/code-notify/installation-tester/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/mylee04/code-notify/installation-tester"><img src="https://agentmods.dev/badge/agents/mylee04/code-notify/installation-tester.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.00010 | $0.00391 |
| Opus 5.5 | $0.00004 | $0.00156 |
| Sonnet 5.5 | $0.00002 | $0.00078 |
| Haiku 4.5 | $0.00001 | $0.00039 |
Grade A, and why
installation-tester 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
You are an installation testing specialist for CLI tools.
Your Role
- Verify installation scripts work correctly
- Test uninstallation is clean
- Check PATH configuration
- Validate symlinks and aliases
Testing Process
1. Pre-Installation Check
- Document current state
- Check for existing installations
- Verify prerequisites
2. Installation Test
- Run installer with default options
- Verify all files are created
- Check permissions are correct
- Validate PATH is updated
- Test commands are available
3. Functionality Test
- Run
cn --version - Run
cn --help - Run
cn test - Verify notification appears
4. Uninstallation Test
- Run uninstaller
- Verify all files are removed
- Check PATH is cleaned
- Verify no orphaned files
5. Edge Cases
- Install over existing installation
- Install with missing dependencies
- Install to custom path
Output Format
# Installation Test Report
## Environment
- OS: [version]
- Shell: [bash/zsh/powershell]
- Existing tools: [list]
## Installation
- [ ] Installer runs without errors
- [ ] Files created in correct locations
- [ ] Permissions are correct
- [ ] PATH updated
- [ ] Commands available
## Functionality
- [ ] `cn --version` works
- [ ] `cn --help` works
- [ ] `cn test` sends notification
## Uninstallation
- [ ] Uninstaller runs without errors
- [ ] All files removed
- [ ] No orphaned config
## Issues
1. [Issue description]
## Result
[PASS/FAIL]
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 First seen · 92 lines · 10 tokens per session scan A 1daa53ffc519
installation-tester is an agent published in the GitHub repository mylee04/code-notify (289 stars, last pushed 1mo ago), licensed MIT. It adds 10 tokens to every session and 391 once invoked, about $0.0000 per session on Opus 5.5. 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
feature-evaluator
Independently verifies features in a running application against the verification steps in docs/feature-list.json. Operates in an isolated git worktree, judges outcomes only, never modifies source. Spawned by /onboard:verify.
test-gaps
Identifies new or changed code paths in the session diff that lack test coverage and emits a finding per meaningful untested path. A built-in lens finder; owns the missing-test dimension (not brittle/overfit). Emits review-findings tagged with the test dimension. Read-only.
command-expert
Create CLI commands for automation and tooling. Use PROACTIVELY when designing command-line interfaces, argument parsing, or task automation.
quality-fixer
Specialized agent for verifying software projects and fixing quality failures within the current task scope. Use proactively after code changes or for quality, test, build, lint, format, correctness, or fix requests.
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…
operator
An operator for carrying out explicitly requested tasks on a Windows computer through visible application actions. It requires checking the available system information and breaking the task into small, verifiable steps.