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/angle_writergit clone --depth 1 https://github.com/elvismusli/onlyharnessWrote 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/elvismusli/onlyharness/angle_writer)<a href="https://agentmods.dev/agents/elvismusli/onlyharness/angle_writer"><img src="https://agentmods.dev/badge/agents/elvismusli/onlyharness/angle_writer.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00033 |
| Opus 5 | $0.00000 | $0.00016 |
| Sonnet 5 | $0.00000 | $0.00007 |
| Haiku 4.5 | $0.00000 | $0.00003 |
Grade A, and why
angle_writer 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 3d 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.
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.
- 3d ago First seen · 7 lines · 0 tokens per session scan A 7b6e055aa7eb
angle_writer 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 33 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
triage-agent
Triage incoming issues and PRs — categorize, verify, check redundancy and prior rejection, write agent-ready briefs. Read-only. Routes: TRIAGE workflow.
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…
progress
$frontend-delivery NEW/REPLAN -> Brain analysis + stack discovery -> close Brain -> one Orchestrator child (intent=deliver) -> controller-action loop -> jira-call -> Primary Controller -> confirmed result -> same Orchestrator -> dispatch-specialist -> Primary Controller -> specialist -> cleanup/close -> result -> same…
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.
issue-tracker
Issues and PRDs for this project live in this repository’s GitHub issue tracker. Use the gh CLI from the repository root so it infers the repository from the current remote.
triage-labels
The skills speak in terms of five canonical triage roles. This file maps those roles to the actual label strings used in this repo's issue tracker.