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 artttj/llama-steve --skill ten-xgit clone --depth 1 https://github.com/artttj/llama-steveWrote 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/artttj/llama-steve/ten-x)<a href="https://agentmods.dev/skills/artttj/llama-steve/ten-x"><img src="https://agentmods.dev/badge/skills/artttj/llama-steve/ten-x/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/artttj/llama-steve/ten-x"><img src="https://agentmods.dev/badge/skills/artttj/llama-steve/ten-x.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.00085 | $0.00986 |
| Opus 5 | $0.00043 | $0.00493 |
| Sonnet 5 | $0.00017 | $0.00197 |
| Haiku 4.5 | $0.00009 | $0.00099 |
Grade A, and why
ten-x 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 10d 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 — 68 lines — stays where its author put it; the contents beside it link to each section on GitHub.
10x — game-changing opportunity finder
Given a product (its current features, its users, and the friction between them), surface the handful of ideas that would make it 10x better — not 10% better. Over-produce candidates here; a separate filter decides what ships. Your job is range and depth, not restraint.
The core question
Most roadmaps are a long list of 10% ideas — polish, parity, nice-to-haves. A 10x idea changes the math of the product: it removes a whole category of friction, collapses three steps into one, or makes the core job feel inevitable instead of effortful. For every idea, ask: "If this shipped, would a user notice within the first thirty seconds, and would they tell someone?" If not, it's a 10%.
Method
- Find the core job. What is the one thing a user hires this product to do? Write it in a single sentence. Everything that doesn't serve that sentence is a candidate for deletion, not addition.
- Walk the real path. Trace the actual flow a user takes to get the core job done — every screen, click, wait, decision, and dead end. The 10x ideas hide in the steps where the user stalls, repeats themselves, or has to think.
- Find the friction. For each stall, name it concretely: what the user is doing, why it's slow or confusing, and what it costs (a drop-off, a support ticket, a moment of doubt).
- Invert the defaults. For every "everyone does it this way," ask what happens if you delete it. The biggest leverage is usually removal, not addition — the feature you cut, the step you skip, the choice you make for the user.
- Reach for the order-of-magnitude version. Don't propose "make onboarding faster." Propose "no onboarding — the product works on the first screen." Push each idea to its boldest honest form.
Writing a strong candidate (descriptions matter)
A weak idea is a label. A strong idea is a detailed, concrete description that a builder could act on and a skeptic could argue with. Each candidate should carry:
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.
- 10d ago First seen · 68 lines · 85 tokens per session scan A e5d64ef0d7fe
ten-x is a skill published in the GitHub repository artttj/llama-steve (1 stars, last pushed 3mo ago), licensed MIT. It adds 85 tokens to every session and 986 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
logging-standards
Structured logging standards: log levels, structured fields, correlation IDs, PII masking, and event naming. TRIGGER when: adding log statements, configuring loggers, or reviewing log output. SKIP: metrics and alerting (use monitoring-observability); error control flow (use error-handling). (Examples use structlog +…
mui-styling
Material-UI (MUI) styling standards: sx-prop priority, theme tokens, spacing scale, responsive design, and accessibility. TRIGGER when: styling MUI components, defining theme tokens, or building responsive layouts. SKIP: component logic and hooks (use react-patterns); cross-stack UX/design decisions (use…
skill-authoring
Methodology for authoring scaffolding-compatible skills: frontmatter contract, body structure, validation. TRIGGER when: running /create-skill, writing or reviewing a SKILL.md file, or deciding if a procedure deserves its own skill. SKIP: distilling a conversation into candidates (use distill); 3-tier memory writes…
sofa-search
Search Stack Overflow for Agents (SOFA) for a peer-verified solution before solving from scratch. TRIGGER when: about to debug an unfamiliar error, integrate a new API/library, or research an unfamiliar pattern, and SOFA is configured. SKIP: trivial/familiar tasks; SOFA unconfigured (no-op); contributing (future…
state-management
Client state management standards: local-vs-global decisions, store structure, selectors, and re-render performance. TRIGGER when: creating a store, managing global state, or deciding local vs global state. SKIP: component/hook structure (use react-patterns); visual styling (use mui-styling). (Examples use Zustand.).
watch-patterns
Correct construction of watchers for long-running operations. TRIGGER when: arming observation of a long-running operation (CI run, deploy, transfer, GC/prune, log stream), writing poll/until loops, or using the Monitor tool. SKIP: defining production alerts/metrics (use monitoring-observability); log formatting (use…