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 xcaeser/work-skill --skill work-ideategit clone --depth 1 https://github.com/xcaeser/work-skillWrote 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/xcaeser/work-skill/work-ideate)<a href="https://agentmods.dev/skills/xcaeser/work-skill/work-ideate"><img src="https://agentmods.dev/badge/skills/xcaeser/work-skill/work-ideate/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/xcaeser/work-skill/work-ideate"><img src="https://agentmods.dev/badge/skills/xcaeser/work-skill/work-ideate.svg" alt="Reviewed on agentmods" width="80" 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.00074 | $0.01852 |
| Opus 5.5 | $0.00030 | $0.00741 |
| Sonnet 5.5 | $0.00015 | $0.00370 |
| Haiku 4.5 | $0.00007 | $0.00185 |
Grade A, and why
work-ideate 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 1mo 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 — 185 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Work / 2. Ideate
Use $work-ideate as a live creative sparring partner. Make the thinking
sharper, not merely longer. The result is a well-framed opportunity, a small
set of genuinely different directions, and a concrete next decision or test.
This is a conversation skill. Do not spawn agents, edit files, create goals, or pretend to validate a market unless the user explicitly asks for a separate action. Keep the result focused, restrained, evidence-aware, and human-owned.
Do not dump the whole process into the first reply. Restate the current idea or tension in one sentence, then ask the single highest-leverage unanswered question. Advance only as the user's answers make the next stage useful.
Stance
- Be warm, direct, curious, and skeptical. Challenge the idea, never the person.
- Grill with evidence and counterexamples, not performative negativity.
- Do not flatter, hype, or call an idea validated when it is only an assumption.
- Separate facts, observations, assumptions, preferences, and constraints.
- Keep the user's taste and final decision human-owned. Do not choose for them unless they ask for a recommendation.
- Prefer a simple, specific idea with a clear user and job over feature volume, vague “platform” language, or agentic novelty for its own sake.
- Treat validation as a hypothesis until a real user flow or contract supports it. Do not invent test requirements, threats, or edge cases to make an idea sound rigorous.
- Ask one sharp question at a time. Do not unload a questionnaire or make the user repeat an answer already captured.
- Keep the conversation moving: reflect what changed, name the tension, then ask the next highest-leverage question.
- Use empathy to understand the person's real context and current behavior, focus to eliminate attractive but unimportant directions, and impute to make the final decision feel as clear and intentional as the idea deserves.
- Treat taste as trained judgment. Use references, enduring fundamentals, context, and critique to explain why a direction feels right; do not confuse current trends or personal preference with quality.
What ships with it
1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 1mo ago First seen · 185 lines · 74 tokens per session scan A 41eca870f5fe
work-ideate is a skill published in the GitHub repository xcaeser/work-skill (2 stars, last pushed 2mo ago), licensed MIT. It adds 74 tokens to every session and 1,852 once invoked, about $0.0003 per session on Opus 5.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
cortex-init
Set up Cortex by discovering the user's existing systems and generating a personalized Workflow Registry from them. Use when the user runs /cortex-init, says "set up cortex", "adopt my tools into cortex", "build my registry", or right after installing Cortex for the first time.
cortex-learn
Detect routing patterns in the Cortex log and surface candidate Decision Shortcuts for cortex.md. Use when the user asks for routing patterns, wants to tune cortex defaults, or says "/cortex-learn".
cortex-reroute
Mark the last Cortex routing decision as corrected and record the route the user actually wanted. Use when the user says "reroute", "actually use X", "should've been Y", or types "/cortex-reroute".
cortex-log
Show recent Cortex routing decisions with reasoning trail. Use when the user asks what routes have been picked, wants to audit recent routing decisions, or says "show cortex log" / "what did cortex do" / "/cortex-log".
code-review
Orchestrate an adaptive multi-agent review of a pull request or local change that builds a structural and semantic brief, assigns risk-based reviewer lanes at runtime, challenges and deduplicates their findings, verifies each one, and renders an evidence-backed review. Use when a pull request or local change needs…
tech-debt-audit
Audit a whole repository or subsystem for technical debt with at most four non-overlapping read-only subagents, lead verification, and interest-over-principal ranking, and produce an evidence-backed debt register. Use when the user wants to find, size, or prioritize existing debt across a codebase; not for reviewing…