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 pyros-projects/limitless --skill naming-as-designgit clone --depth 1 https://github.com/pyros-projects/limitlessWrote 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/pyros-projects/limitless/naming-as-design)<a href="https://agentmods.dev/skills/pyros-projects/limitless/naming-as-design"><img src="https://agentmods.dev/badge/skills/pyros-projects/limitless/naming-as-design/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/pyros-projects/limitless/naming-as-design"><img src="https://agentmods.dev/badge/skills/pyros-projects/limitless/naming-as-design.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.00105 | $0.00712 |
| Opus 5.5 | $0.00042 | $0.00285 |
| Sonnet 5.5 | $0.00021 | $0.00142 |
| Haiku 4.5 | $0.00011 | $0.00071 |
Grade A, and why
naming-as-design 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 — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Naming as Design
Overview
This skill treats naming as structural design, not editorial polish.
The names a product uses are the user's ontology. If the nouns drift, the mental model drifts with them. This skill helps clean up that conceptual layer before confusion becomes normal.
When to Use
Use this when:
- the same concept is called different things in different places
- new features are creating noun sprawl
- the product feels harder to explain than it should
- an API, UI, and docs seem to describe different worlds
Do not use this for tiny wording tweaks that have no model-level consequence.
What to Produce
Map the current conceptual language:
- core nouns
- overlaps and collisions
- missing distinctions
- terms that sound similar but mean different things
- places where renaming would clarify the model
Then recommend a cleaner vocabulary and explain what changes in the user's understanding if the rename is adopted.
Working Loop
-
Inventory the nouns. Pull the important terms from the UI, docs, APIs, settings, and conversation around the product.
-
Map the collisions. Where are multiple names pointing at one concept? Where is one name carrying too many meanings?
-
Find the real model. Decide what conceptual world the product is actually trying to create for the user.
-
Rename toward clarity. Recommend the vocabulary that makes the model feel singular, legible, and easier to think with.
Suggested Output Shape
Current concept mapConflicts and collisionsWhat mental model the current language createsRecommended vocabularyWhat becomes easier to understand after renaming
Tiny Example
Current concept map: The UI saysWorkspace, the API saysProject, and the docs sayEnvironment.Conflicts and collisions: Three names are pointing at the same thing.What mental model the current language creates: The product feels like it has three overlapping containers.Recommended vocabulary: UseWorkspaceeverywhere.What becomes easier to understand after renaming: Users can form one stable picture of where their work lives.
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 · 89 lines · 105 tokens per session scan A 0b8956a16e2e
naming-as-design is a skill published in the GitHub repository pyros-projects/limitless (2 stars, last pushed yesterday), licensed MIT. It adds 105 tokens to every session and 712 once invoked, about $0.0004 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
example-feature-generator
Generate boilerplate for new features following project conventions. Use when user says "create feature", "add feature", or "new feature scaffolding".
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
agent-flutter-developer
Specialist subagent: Flutter/Dart cross-platform development, Riverpod state management, and platform channels specialist. Use when building Flutter apps, implementing state management, or working with native platform features. Trigger phrases: Flutter, Dart, Riverpod, Bloc, widget, MaterialApp, GoRouter, platform…
electron-desktop
Desktop application development with Electron for Windows, macOS, and Linux. Use when building cross-platform desktop apps, implementing native OS features, or packaging web apps for desktop.
investment-memo-generator
Investment memo creation combining financial analysis, document generation, and structured templates. Use when creating investment memos, pitch decks, deal summaries, or investment committee materials.
agent-seo-specialist
Specialist subagent: Technical SEO, structured data, Core Web Vitals, meta tags, and Schema.org specialist. Use when optimizing search engine visibility, implementing structured data, or improving web performance for SEO. Trigger phrases: SEO, meta tags, Open Graph, Schema.org, structured data, sitemap, robots.txt…