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/rana/skills/explore-actgit clone --depth 1 https://github.com/rana/skillsWrote 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/rana/skills/explore-act)<a href="https://agentmods.dev/commands/rana/skills/explore-act"><img src="https://agentmods.dev/badge/commands/rana/skills/explore-act.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.00183 |
| Opus 5 | $0.00000 | $0.00092 |
| Sonnet 5 | $0.00000 | $0.00037 |
| Haiku 4.5 | $0.00000 | $0.00018 |
Grade A, and why
explore-act 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 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.
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.
What it actually says
Deep multi-dimensional perspective — biased toward action.
Read all project markdown documents to ground your exploration in the project's actual state.
$ARGUMENTS
Be proactive — propose concrete actions, not just observations. For every insight, answer:
- What specific change would this imply? (code, design, decision, or document)
- Where exactly does it belong? (file, section, Identifier number, ADR, etc)
- What's the next step to act on it?
Present proposed changes as a clear action list the user can approve, reject, or refine. Do not modify any files — document only.
Output
Deliver highest-priority findings first. Dense observations, not expansive prose.
What questions would I benefit from asking?
What am I not asking?
What constraints am I unconsciously accepting?
Where am I compressing prematurely, and where am I expanding without structure?
You have complete design autonomy.
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 · 27 lines · 0 tokens per session scan A bf52817a0bb9
explore-act is a command published in the GitHub repository rana/skills (1 stars, last pushed 5mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 183 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 commands, from other repositories
init
Install the formatters this repository needs, with every command visible before it runs.
brand-generate
Generate an on-brand document from a saved Brand Profile.
genshijin-compress
Markdown・テキストファイルを原始人形式へ安全圧縮.
standup
Show a daily standup summary with completed, in-progress, and blocked tasks across all active epics.
wp-polylang
Translate an existing WordPress site into a second language using Polylang.
check-dev
Type-check a Z specification with fuzz.