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/elvismusli/onlyharness/source_readergit clone --depth 1 https://github.com/elvismusli/onlyharnessWhat 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.00037 |
| Opus 5 | $0.00000 | $0.00018 |
| Sonnet 5 | $0.00000 | $0.00007 |
| Haiku 4.5 | $0.00000 | $0.00004 |
Grade A, and why
source_reader 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 today.
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.
The source is not reproduced here
No licence file
A repository with no LICENSE is all rights reserved by default, so the body is not copied here. The metadata, the measurements and the link are.
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.
- today First seen · 7 lines · 0 tokens per session scan A 0017421ac0a2
source_reader is an agent published in the GitHub repository elvismusli/onlyharness (0 stars, last pushed 1mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 37 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-31.
Other agents, from other repositories
claude-md-compliance-checker
Use after completing implementation tasks to verify changes comply with CLAUDE.md project rules — file boundaries (src/, e2e/ only), path alias usage (@/), feature-slice architecture, AIDEV-NOTE comments, scope creep, and forbidden actions (unauthorized commits, API contract changes). NOT for general code quality …
charter
You are one subagent in an autonomous browser-game agent — a durable operator that builds a single game and then runs it like a real studio: bug fixes, new features, gameplay and balance iteration, new content, and polish. Operate autonomously: don't pause to ask the operator questions, request permission, or wait to…
code-quality-pragmatist
Use after writing or modifying code to review for over-engineering, unnecessary complexity, anti-patterns, and feature-slice architecture compliance. Checks that code stays simple, pragmatic, and aligned with actual project needs rather than theoretical best practices.
ultrathink-debugger
Use when encountering bugs, errors, unexpected behavior, or system failures that require deep investigation and root cause analysis. Excels at diagnosing complex issues, tracing execution paths, identifying subtle bugs, and implementing robust fixes that don't introduce new problems. Perfect for production issues…
devops-engineer
Handles infrastructure, deployments, database and migrations, environment variables, CI/CD, secrets, and build or runtime troubleshooting. Use proactively for config changes, failed deploys, environment setup, or hardening the pipeline.
board-haiku
Mechanical delivery-board executor (haiku tier). Use for grep-and-replace passes, running gates, board/LOG hygiene, and other single-surface contracts with zero design judgment. Also see board-verifier for verification work.