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 commands/mnvsk97/eyeroll/api-watchgit clone --depth 1 https://github.com/mnvsk97/eyerollWrote 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/commands/mnvsk97/eyeroll/api-watch)<a href="https://agentmods.dev/commands/mnvsk97/eyeroll/api-watch"><img src="https://agentmods.dev/badge/commands/mnvsk97/eyeroll/api-watch.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.00268 |
| Opus 5 | $0.00000 | $0.00134 |
| Sonnet 5 | $0.00000 | $0.00054 |
| Haiku 4.5 | $0.00000 | $0.00027 |
Grade A, and why
api-watch scanned grade A with 1 finding 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 4d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
curl -s -X POST "$EYEROLL_API_URL/api/watch" \ What it actually says
Analyze a video URL or local file using the eyeroll hosted API.
Usage
/eyeroll:api-watch <url-or-path> [context]
What this does
- Reads
EYEROLL_API_URLfrom the environment, defaulting to the hosted API URL - POSTs the source and optional context to
/api/watch - Returns intent, repo guess, handoff recommendation, confidence, and the structured markdown report
Steps
-
Set
EYEROLL_API_URLtohttps://api.eyeroll.devif not already set. -
Call the hosted API. Authentication is handled by the deployment platform, not by eyeroll API keys.
-
Run:
curl -s -X POST "$EYEROLL_API_URL/api/watch" \
-H "Content-Type: application/json" \
-d "{\"source\": \"$ARGUMENTS\", \"context\": null}"
-
Display the structured response:
- intent
- repo_guess
- handoff_recommended
- confidence
- report
-
If the response status is 401 or 403, tell the user the hosted endpoint authentication is blocking the request and they should authenticate through the TrueFoundry-protected route.
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.
- 4d ago First seen · 36 lines · 0 tokens per session scan A a18b5e26c0c7
api-watch is a command published in the GitHub repository mnvsk97/eyeroll (17 stars, last pushed 3mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 268 tokens. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other commands, from other repositories
frontend
Injects context of all relevant cli files.
cleanup-back-to-main
Go back to main and clean up the branch.
context
项目上下文管理：初始化 .context 目录、记录决策日志、压缩归档、查看历史.
spec-research
需求 → 约束集（并行探索 + OPSX 提案）.
spec-design
Create comprehensive technical design for a specification.
release
Ship a stable cmux release built by CI: bump version, update changelog, open a PR, merge, tag, then GitHub Actions builds, signs, and publishes.