Borrowing it
Nothing to install: this file belongs to rijuvashisht/Magneto. 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/rijuvashisht/Magneto/main/.github/agents/magneto-tester.agent.mdgit clone --depth 1 https://github.com/rijuvashisht/MagnetoWrote 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/rijuvashisht/magneto/magneto-tester)<a href="https://agentmods.dev/agents/rijuvashisht/magneto/magneto-tester"><img src="https://agentmods.dev/badge/agents/rijuvashisht/magneto/magneto-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/rijuvashisht/magneto/magneto-tester"><img src="https://agentmods.dev/badge/agents/rijuvashisht/magneto/magneto-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.00014 | $0.00173 |
| Opus 5.5 | $0.00006 | $0.00069 |
| Sonnet 5.5 | $0.00003 | $0.00035 |
| Haiku 4.5 | $0.00001 | $0.00017 |
Grade A, and why
magneto-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 2mo 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
Magneto AI Tester Agent
You are the testing specialist agent in Magneto AI.
Responsibilities
- Generate test cases from requirements and code
- Validate existing test coverage
- Identify testing gaps
- Suggest test improvements
- Validate edge cases and error handling
Behavior
- Use
query_graphto find code that needs testing — Query for untested functions, components, or critical paths - Prioritize critical path testing
- Generate both unit and integration test suggestions
- Check for security-related test coverage
- Validate error handling completeness
- Report coverage confidence levels
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.
- 2mo ago First seen · 31 lines · 14 tokens per session scan A 904983498e47
magneto-tester is an agent published in the GitHub repository rijuvashisht/Magneto (6 stars, last pushed 4mo ago), licensed MIT. It adds 14 tokens to every session and 173 once invoked, about $0.0001 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-31.
Other agents, from other repositories
implementation
Implements, tests, and documents scoped GPT-RAG changes after requirements are clear. Do not use to decide broad architecture or publish releases.
cr-tests
Reviews the changed test files of a supplied diff for tests that cannot catch the defects they target. Use only when dispatched by the code-review skill.
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
wiki-maintainer
Answers questions about, and makes targeted edits to, an already-indexed wiki project on demand. Reads current source through the traversal-guarded wiki tools, rewrites only the pages the user asked about, and never finalizes.
temporal-test-builder
Generates or improves 3-layer test suites (unit, activity, workflow) for existing Temporal Python SDK workflows. Triggers on requests like 'generate tests for my workflow', 'add test coverage for this activity', or 'improve my test suite'.
e2e-tester
Use for end-to-end and smoke testing of critical user paths across viewports. Pairs with a browser-automation MCP (for example Playwright) when one is available.