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.
git clone --depth 1 https://github.com/evan043/claude-cli-advanced-starter-packWrote 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/evan043/claude-cli-advanced-starter-pack/landing-page-toggle.template)<a href="https://agentmods.dev/commands/evan043/claude-cli-advanced-starter-pack/landing-page-toggle.template"><img src="https://agentmods.dev/badge/commands/evan043/claude-cli-advanced-starter-pack/landing-page-toggle.template.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.00000 | $0.01414 |
| Opus 5 | $0.00000 | $0.00707 |
| Sonnet 5 | $0.00000 | $0.00283 |
| Haiku 4.5 | $0.00000 | $0.00141 |
Grade A, and why
landing-page-toggle.template 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 8d 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.
How it starts
The opening of the file, as written. The whole thing — 182 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codex Runtime Compatibility
This prompt was authored for Claude-style slash workflows. In Codex runtime, adapt tool calls as follows:
AskUserQuestion=> ask the user directly in chat.WebSearch/WebFetch=> use available web tools (search_query,open,find) and cite links.Read/Write=> use shell/filesystem tools in this workspace.- Claude-only MCP calls (for example Playwright MCP names) => use available equivalents or clearly state fallback.
- Keep intent and output format identical; only adapt execution mechanics.
description: Toggle landing page on/off in production model: haiku allowed-tools:
- Read
- Write
- Edit
- Bash
Toggle Landing Page
{{#if panel_config}}
Panel config gate: If panel_config.features.landing_page_generator === false, skip this entire command.
Display: "Landing page toggle skipped (disabled in panel config)."
{{/if}}
Toggle the landing page on or off. When enabled, the root route shows the marketing landing page. When disabled, the root route goes directly to the main application.
What This Command Does
- Updates
{{landingPage.configPath}}to setenabled: trueorfalsebased on argument - Updates timestamp and modifier
- Rebuilds the frontend
- Deploys to production
Usage
/landing-page-toggle enable # Enable landing page
/landing-page-toggle disable # Disable landing page
/landing-page-toggle # Toggle current state (enable if disabled, disable if enabled)
Effect
When Enabled
- Result: Root URL ({{deployment.frontend.url}}) → Landing Page (with "Get Started" or "Sign In" button)
When Disabled
- Result: Root URL ({{deployment.frontend.url}}) → Main App (direct authentication or dashboard)
Implementation
You should:
- Read the current config at
{{landingPage.configPath}}- If file doesn't exist, create it with default structure:
{ "enabled": false, "routes": [], "viewports": [], "devices": [], "gif": { "frameDelay": 2000, "quality": 10, "maxSize": 5242880 }, "outputDir": "{{landingPage.outputDir}}", "baseUrl": "{{deployment.frontend.url}}", "lastModified": "", "modifiedBy": "" }
- If file doesn't exist, create it with default structure:
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.
- 8d ago First seen · 182 lines · 0 tokens per session scan A 6609879c5b9e
landing-page-toggle.template is a command published in the GitHub repository evan043/claude-cli-advanced-starter-pack (61 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,414 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-30.
Other commands, from other repositories
worktree-cleanup
A command for removing a Git worktree, which is a separate working folder linked to the same repository, after its pull request is merged.
quick-commit
A quick Git command for committing and pushing a small code change. Git is the tool that records code versions and sends them to a shared repository.
security-review
A security review procedure based on CWE, a list of common software weaknesses, and STRIDE, a method for identifying threats to a system.
test-suite
Run comprehensive test suite with coverage analysis.
pull-repos
Pull all repos (parent + marketplace clones + configured project repos).
security-scan
Run security audit on codebase.