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 skills/treylom/thiscodex/setupnpx skills add treylom/ThisCodex --skill setupgit clone --depth 1 https://github.com/treylom/ThisCodexWhat 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.00043 | $0.03463 |
| Opus 5 | $0.00022 | $0.01732 |
| Sonnet 5 | $0.00009 | $0.00693 |
| Haiku 4.5 | $0.00004 | $0.00346 |
Grade B, and why
setup scanned grade B 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 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.
Reads agent configuration directoriesmediumAgent snooping
.claude/, .codex/, .gemini/ hold keys, settings and other credentials a mod has no legitimate need for.
`trusted_hash` is written to `~/.codex/config.toml`). Verify a Stop How it starts
The opening of the file, as written. The whole thing — 210 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ThisCodex Setup Skill
Generated through the mandatory /prompt workflow:
/prompt --batch GPT-5.6 상세 ThisCodex setup skill: create a step-by-step installer-facing skill that invokes thiscodex init, keeps guided onboarding distinct from placement, uses tmux only, explains YOLO safely, and asks progress_report_cadence.
Goal
Guide thiscodex setup / thiscodex init without inventing paths or silently
skipping decisions.
Automatic handoff inventory (runtime source of truth)
install/automation-policy.yaml owns the machine-readable names below. In
automatic mode, every user-facing manual instruction must first pass
thiscodex automation-gate; copy its receipt_marker unchanged into the
Discord message together with <!-- thiscodex-manual-handoff -->. The bridge
and the PreToolUse hook reject a handoff without a current-turn receipt.
| Gate | Automatic action before handoff | Human-only / terminal reason |
|---|---|---|
host_wsl_install_consent |
inspect host/WSL state | host install consent |
host_tmux_install_consent |
inspect tmux state | host install consent |
codex_privilege_config_consent |
inspect safe/YOLO config | privilege-boundary consent |
codex_hook_trust_approval |
wire and probe the hook | Codex /hooks trust approval |
shell_profile_persistence |
generate a sourceable block | persistent profile edit consent |
daemon_start_consent |
materialize and verify runner | daemon start consent |
superpowers_install_consent |
detect the skill/plugin | install consent |
github_auth_login |
run secret-safe auth detection | account login |
codex_discord_mcp_config_consent |
inspect current MCP config | config edit consent |
browser_provider_install_declined |
offer provider registration | explicit operator decline |
browser_provider_setup |
register, restart, and re-detect | observed provider failure |
browser_provider_ready |
inspect a callable browser tool | successful provider-flow terminal |
discord_portal_login |
inspect with the bound provider | credentials/MFA |
discord_hcaptcha |
inspect with the bound provider | CAPTCHA |
discord_reset_token_modal |
inspect with the bound provider | password/MFA modal |
discord_desktop_approval |
attempt with the bound provider | observed uncontrollable-window failure |
discord_portal_complete |
inspect the final portal state | successful portal-flow terminal |
token_direct_entry |
attempt model-blind clipboard receipt | observed clipboard failure, then user-only secret entry |
slack_browser_login |
inspect with the bound provider | credentials/MFA |
slack_browser_auth |
ticket → confirm → challenge with the bound provider | observed browser failure |
slack_browser_auth_complete |
inspect signed-in Slack state | successful auth-flow terminal |
slack_workspace_admin_approval |
inspect workspace requirement | admin approval |
slack_app_reinstall_approval |
inspect requested scopes | OAuth reinstall approval |
slack_native_host_install_consent |
detect native-host path | native install consent |
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 · 210 lines · 43 tokens per session scan B 55afc9dd45dc
setup is a skill published in the GitHub repository treylom/ThisCodex (17 stars, last pushed 17d ago), licensed MIT. It adds 43 tokens to every session and 3,463 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it B with 1 finding (reads agent configuration directories). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…