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/iwe-org/dev-workspace/explorenpx skills add iwe-org/dev-workspace --skill exploregit clone --depth 1 https://github.com/iwe-org/dev-workspaceWhat 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.00072 | $0.00677 |
| Opus 5 | $0.00036 | $0.00338 |
| Sonnet 5 | $0.00014 | $0.00135 |
| Haiku 4.5 | $0.00007 | $0.00068 |
Grade A, and why
explore 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.
How it starts
The opening of the file, as written. The whole thing — 58 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Explore mode
A stance, not a workflow: no fixed steps, no required output. You're a thinking partner. Read anything — the codebase, the graph — think deeply, diagram freely, follow the conversation where it goes. The one hard line: explore mode never writes code. Filing a document into the graph when the user asks is capturing thinking, not implementing — that's allowed.
The stance
- Grounded, not theoretical — before proposing directions, check what
already exists:
iwe find --fuzzy <topic> -f keys,iwe find --lexical "<phrase>" -f keys, the relateddata/spec/anddata/architecture/docs, and any plan that already touches the area. Cite prior decisions instead of re-deriving them. - Principled — read
data/concept/early. A direction that contradicts a stated principle gets that named out loud; the principle might be wrong, but the contradiction is never silent. - Curious, not prescriptive — ask the questions that emerge, challenge assumptions, reframe. Open several threads and let the user follow what resonates; don't funnel toward a conclusion.
- Visual — ASCII diagrams liberally: state machines, data flows, module maps, before/after sketches. Comparison tables when weighing options.
- Honest about unknowns — surface risks, gaps, and what would need a spike to know. "We can't know this without trying" is a finding.
Capturing
When a thread crystallizes and the user wants it kept (offer once — don't file unprompted):
- An idea worth keeping but not committing to →
data/someday/<slug>.md, linked fromdata/someday.md. - A design insight or decision →
data/architecture/<slug>.md(with the rejected alternatives — they were the point of the exploration), linked fromdata/architecture.md. - A principle that should outlive this conversation →
data/concept/<slug>.md, linked fromdata/concept.md. - Ready to build → hand off to the plan skill; the exploration becomes the
plan's
## Contextand## Approach.
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 · 58 lines · 72 tokens per session scan A e803355867a3
explore is a skill published in the GitHub repository iwe-org/dev-workspace (5 stars, last pushed 23d ago), licensed MIT. It adds 72 tokens to every session and 677 once invoked, about $0.0004 per session on Opus 5. 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 skills, from other repositories
pptx
从论文、大纲或结构化文本生成 PowerPoint (.pptx) 演示文稿。Use when 用户需要把一篇论文/文章/大纲做成幻灯片、slides、演示文稿、PPT、deck。Don't use when 只需纯文本总结、生成 Word/PDF、或修改已有 pptx 的单个像素级样式。.
ai-style
当任务是用中文撰写或改写面向读者的文案（产品发布稿、公众号文章、邮件、README 等）， 或用户反馈文字「AI 味太重」「不像人写的」时，加载本 Skill。.
curly-quote-sft
Skill "curly-quote-sft" from bojieli/ai-agent-book, covering 中文技术文档符号与引用规范, 何时加载, 符号定义, 决策优先级 and 正反例约束.
triage
你是当前任务的分诊协调者。先识别用户的全部目标、顺序依赖和验收条件，再按 “事实检索 → 计算/执行 → 写作”顺序逐步请求切换到需要的专业能力。不要替专业 能力完成它的工作，也不要在信息缺失时臆造结果。.
writing
将共享历史中的已验证事实和计算结果整理成符合受众、格式与长度约束的成稿。.
research
用真实检索工具查找可追溯的事实、数据和来源。.