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/caffnoir59/codex-seo/technical-agentgit clone --depth 1 https://github.com/CaffNoir59/codex-seoWhat 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.00053 |
| Opus 5 | $0.00000 | $0.00026 |
| Sonnet 5 | $0.00000 | $0.00011 |
| Haiku 4.5 | $0.00000 | $0.00005 |
Grade A, and why
technical-agent 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 2d 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.
- 2d ago First seen · 4 lines · 0 tokens per session scan A 16016d85124b
technical-agent is an agent published in the GitHub repository CaffNoir59/codex-seo (1 stars, last pushed 1mo ago), with no licence file. It costs nothing until one of its globs matches a file; then it loads 53 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
bxc-web-researcher
Use proactively for any task needing fresh web data — answering a question from live sources, multi-source research, scraping a page/site, extracting structured data, monitoring a SERP, or checking what a URL actually contains. Drives the bxc CLI (search/scrape/recon/detect/mirror) end-to-end and returns a sourced…
bxc-scrape-debugger
Use when a Bxc scraper fails, gets blocked (403/429/captcha), or returns empty/wrong data. Inspects HTML / headers / console dumps and proposes the next profile escalation step.
bxc-scraper-creator
Creator of new bxc-style scraper packages. Knows the monorepo layout under packages/, CLI registration pattern, profile mapping, test scoping, publishing as @aphrody/ on GitHub Packages, and how to make a new scraper (e.g. for a new site or API) follow the same quality and integration as fut, voiranime, xcom, zukan…
ui-reviewer
Find UI issues that code-level analysis (scout, codemap, dependencygraph) cannot detect. Launches a real browser to check rendering, visual states, interactions, a11y, and runtime errors. Use after FE implementation to catch issues invisible to static analysis.
agent-creator
Agent "agent-creator" from aphrody-code/bxc, covering agent created: [identifier], configuration, file created, how to use and next steps.
plugin-validator
Agent "plugin-validator" from aphrody-code/bxc, covering plugin validation report, plugin: [name], summary, critical issues ([count]) and warnings ([count]).