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 skills add tt-a1i/agents-market --skill codex-skillgit clone --depth 1 https://github.com/tt-a1i/agents-marketWrote 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/skills/tt-a1i/agents-market/codex-skill)<a href="https://agentmods.dev/skills/tt-a1i/agents-market/codex-skill"><img src="https://agentmods.dev/badge/skills/tt-a1i/agents-market/codex-skill.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.1 | $0.00043 | $0.00724 |
| Opus 5 | $0.00022 | $0.00362 |
| Sonnet 5 | $0.00009 | $0.00145 |
| Haiku 4.5 | $0.00004 | $0.00072 |
Grade A, and why
agents-market-installer 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 7d 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.
This is a copy
91% identical to agents-market-installer — 4 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 44 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Agents Market Installer
Use the local agents-market CLI to recommend and install specialized coding subagent packs.
Workflow
- Inspect the repository briefly so you understand the project type.
- If the user provides a registry URL or bundle path, run
agents-market registry info --registry <source> --json, summarize the source/version/checksum, then runagents-market registry lock --registry <source>after confirmation. - Run
agents-market apply --target all --jsonto preview the recommended pack, audit, policy result, and file diff. - If the user names a pack, run
agents-market apply <pack-id> --target all --jsoninstead. - If the user wants a small custom set, run
agents-market search <query> --json, create a pack withagents-market pack create <pack-id> --agent <ids...> --out ./registry/packs, then preview it withagents-market apply <pack-id> --target all --json. - Explain target files, permission implications, policy findings, warnings, and source/license status.
- After user confirmation, run
agents-market apply <pack-id> --target all --yes. - Verify install state with
agents-market status --json,agents-market outdated --json, andagents-market doctor --strict --json. - Summarize installed files, pack version state, health warnings, and how the user can invoke the new agents.
Target Selection
- Use
--target claudefor Claude Code only. - Use
--target codexfor Codex only. - Use
--target opencodefor OpenCode only. - Use
--target allwhen the user wants cross-tool support or does not know which tool they will use.
Safety
Prefer apply because it combines recommendation, audit, policy, diff, and guarded install. Use lower-level commands such as recommend, audit, policy check, diff, and install only when the user needs custom control or troubleshooting.
Use search --json for discovery. Do not use list --agents --json --full unless the user explicitly asks to inspect full prompt bodies; default list --agents --json is a compact index, and --full can be large on community registries.
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.
- 7d ago First seen · 44 lines · 43 tokens per session scan A 8e6de9f508a3
agents-market-installer is a skill published in the GitHub repository tt-a1i/agents-market (6 stars, last pushed 2d ago), licensed MIT. It adds 43 tokens to every session and 724 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. It is 91% identical to agents-market-installer, differing in 4 lines, and is treated as a copy.
Other skills, from other repositories
agentplane
Use when a repository uses AgentPlane or the user wants a governed git-native workflow for planning, task execution, verification, and closure.
expo-eas-update
Publishing OTA updates with EAS Update, channels, runtime versions, branch management, and rollback strategy. Triggers on eas update, ota, over-the-air, runtime version, channel, branch, rollback, embedded update, asset selection, expo-updates, hot update, partial release, release cohort.
pentest-credentials
Credential testing methodology — hash crack selection, wordlist generation, password spray (advisory), default cred audit. Triggers on credential testing, hash crack, Hashcat, John the Ripper, password spray, wordlist generation, cupp, CeWL, Crunch, hashid, default password, credential stuffing.
pentest-ctf
CTF (Capture the Flag) challenge solving advisory — HackTheBox, TryHackMe, PicoCTF, web/pwn/rev/crypto/forensics. Triggers on CTF, HackTheBox, HTB, TryHackMe, THM, PicoCTF, OverTheWire, pwn, reverse engineering, crypto challenge, forensics challenge, stego.
pentest-exploit-chain
Multi-step exploit chain analysis — linking low/medium severity findings into a critical chain, stealth+impact scoring advisory. Triggers on exploit chain, attack chain, chain analysis, multi-step attack, kill chain, attack path, stealth scoring, impact analysis.
pentest-orchestrator
Authorized penetration testing engagement orchestrator — scope declaration, OPSEC tagging, evidence-handling discipline. Triggers on pentest, penetration test, red team, engagement, ROE, scope, security assessment, vulnerability assessment, ethical hacking. ADVISORY/DEFENSIVE: does not run live exploits; methodology…