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 scott-fryxell/brayness --skill uselessgit clone --depth 1 https://github.com/scott-fryxell/braynessWrote 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/scott-fryxell/brayness/useless)<a href="https://agentmods.dev/skills/scott-fryxell/brayness/useless"><img src="https://agentmods.dev/badge/skills/scott-fryxell/brayness/useless/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/scott-fryxell/brayness/useless"><img src="https://agentmods.dev/badge/skills/scott-fryxell/brayness/useless.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.00115 | $0.05869 |
| Opus 5 | $0.00057 | $0.02934 |
| Sonnet 5 | $0.00023 | $0.01174 |
| Haiku 4.5 | $0.00012 | $0.00587 |
Grade A, and why
useless 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 yesterday.
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 — 288 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Useless
Semantic HTML first. Style the platform. Not components - elements.
One markup decision pays seven times. Microdata is not an SEO garnish bolted
on at the end. itemid, itemprop and itemtype are the same identifiers the
stylesheet selects on, the layout reads with :has(), the data layer parses,
the app holds document state in instead of a store, the storage path is built
from, and the database lists as collections. Write the element once and every
layer downstream already knows what it means.
| Layer | What reads the markup |
|---|---|
| SEO | itemtype / itemprop - Schema.org, read by crawlers and any other reader |
| Design | the attribute is the selector - address[itemscope], time |
| Layout | :has() on something real - figure:has([itemtype='/posters']), no wrapper invented to hold it |
| Data model | itemprop_value() reads <time datetime>, <img src>, <a href> - the element says how to read it |
| Store replacement | no Pinia, no Vuex. get_item(elements, itemid) queries the rendered DOM for a document |
| File storage | itemid is the path - /+author/posters/1712000000000 becomes people/+author/posters/1712000000000.html.gz |
| NoSQL database | Directory lists a folder as a collection, cached in idb. Storage is the database; the HTML is the row |
That is the whole argument. Everything below is what follows from taking it seriously, and the cost of not: an invented class is a name that only one layer understands, so the other six have to be told separately.
This skill is a method, demonstrated through one project's answer to it. That project is realness (work/realness): a rotoscoping tool that traces photos into layered SVG posters. Sections pair a general rule with a "realness's instance" callout. When you bring this to a different project, keep the method and re-derive the specifics - a client's unit, ratio, and palette are not this project's.
What ships with it
7 files 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.
- yesterday First seen · 288 lines · 115 tokens per session scan A 05fa944e84fd
useless is a skill published in the GitHub repository scott-fryxell/brayness (120 stars, last pushed yesterday), licensed MIT. It adds 115 tokens to every session and 5,869 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-09-08.
Other skills, from other repositories
chakra-ui-builder
Build responsive, accessible UI components and layouts using Chakra UI v3, install or configure Chakra UI in new and existing projects, and design scalable themes using tokens, semantic tokens, recipes, and slot recipes. Use this skill whenever a user asks to build, create, or generate any UI component, page, form…
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.
frontend-visual-qa
Audits already-rendered web, landing-page, HTML deck/slide, browser tool/game, dashboard/admin, design-system, and desktop UIs using real-browser or native-app journeys, inspected screenshots, DOM geometry, responsive or projection viewports, and a bundled Playwright sweep. Use after UI implementation to find…
prototype-web
A clickable, high-fidelity web product prototype with navigation, a hero section, feature cards, steps, social proof, and optional pricing. It is designed to resemble a finished landing page while remaining a prototype.
waitlist-page
A simple waitlist page for collecting email addresses from people interested in a new product or early-access release.
tailwindcss
Tailwind CSS v4 conventions — semantic design tokens for theme-safe styling, mobile-first responsive layouts, and v4-first utilities. Use when styling components or writing className utilities with Tailwind. Don't use for plain CSS, CSS-in-JS (styled-components, emotion), or other utility frameworks.