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 lenxism/ives --skill craft-philosophygit clone --depth 1 https://github.com/lenxism/ivesWrote 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/lenxism/ives/craft-philosophy)<a href="https://agentmods.dev/skills/lenxism/ives/craft-philosophy"><img src="https://agentmods.dev/badge/skills/lenxism/ives/craft-philosophy.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.00111 | $0.01145 |
| Opus 5 | $0.00056 | $0.00573 |
| Sonnet 5 | $0.00022 | $0.00229 |
| Haiku 4.5 | $0.00011 | $0.00114 |
Grade A, and why
craft-philosophy 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 — 110 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Craft Philosophy
These aren't rules to follow mechanically — they're a mindset to internalize. When you build interfaces, you're creating something people will see, touch, and feel. That demands intention.
The Practice of Noticing
Your first reaction to anything is almost always shallow. Noticing is the practice of staying with it longer — truly considering what you're looking at, what you're feeling, and why.
When building or reviewing an interface, actively notice:
- Moments of hesitation — What caused it? Uncertainty? Lack of trust? Ambiguity?
- Expectation gaps — Where does the mental model break?
- Emotional shifts — What triggers annoyance, delight, or confusion? Pinpoint the moment.
- What's missing — What were you looking for that isn't there?
- How it looks — Does it feel cheap or crafted? Is typography comfortable? Do colors work together? Is there clear hierarchy?
- How it feels — Fast or sluggish? Responsive or disconnected? Durable or fragile?
Every reaction is data. When something feels off, articulate why. When something feels right, understand what's making it work.
In practice
After every first pass of output:
- Pause. Look at it as a user would. What's your honest reaction?
- Identify at least one thing that feels "just okay" and push it further.
- Ask: if someone with exceptional taste looked at this, what would they notice that I missed?
Uncommon Care
The difference between good and great work is how much the creator cared. The willingness to go further than expected — to spend more time than feels reasonable — separates memorable from forgettable.
"Sometimes magic is just someone spending more time on something than anyone else might reasonably expect." — Penn & Teller
Where care shows up
True care shows up in places most people overlook:
- Edge cases and error states
- Conditions only a few users might ever see
- Transitions between states, not just the states themselves
- The loading experience, not just the loaded result
- The empty state, not just the populated one
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 · 110 lines · 111 tokens per session scan A 57187c062de5
craft-philosophy is a skill published in the GitHub repository lenxism/ives (5 stars, last pushed 6mo ago), licensed MIT. It adds 111 tokens to every session and 1,145 once invoked, about $0.0006 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
webgl-holographic-foil
A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
html-ppt-taste-brutalist
16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).
visual-ralph
Visual Ralph orchestration for frontend UI from generated references, static references, or live URL targets, using $ralph with built-in visual verdict and pixel-diff evidence until the implementation matches and leaves a reproducible design system.
accessibility
Consolidated accessibility skill entrypoint for WCAG 2.2, ARIA Authoring Practices, cognitive accessibility, Section 508, EN 301 549, design intent verification, and the Accessibility Planner workflow.
make-resume
A Chinese-language tool for creating editable HTML resumes that can be changed in a browser and printed to PDF. It uses available resume templates when they are installed and otherwise provides a simpler fallback.