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 local-mythologygit 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/local-mythology)<a href="https://agentmods.dev/skills/pyros-projects/limitless/local-mythology"><img src="https://agentmods.dev/badge/skills/pyros-projects/limitless/local-mythology/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/local-mythology"><img src="https://agentmods.dev/badge/skills/pyros-projects/limitless/local-mythology.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.00104 | $0.00747 |
| Opus 5 | $0.00052 | $0.00374 |
| Sonnet 5 | $0.00021 | $0.00149 |
| Haiku 4.5 | $0.00010 | $0.00075 |
Grade A, and why
local-mythology 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 9d 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 — 90 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Local Mythology
Overview
This skill turns a project's implicit identity into explicit language.
It is for the moments when a product clearly wants to be something, but nobody has written down what it believes, what it refuses to become, or what emotional rules it seems to live by.
When to Use
Use this when:
- the product feels interesting but hard to describe cleanly
- the team keeps making decisions without a stable point of view
- naming, tone, or feature direction are drifting
- the project needs a compact articulation of its identity
Do not use this for generic brand copy or marketing fluff. This skill is for extracting the inner rules of the project itself.
What to Produce
Build a small lorebook with things like:
- what this project believes
- what it refuses to become
- recurring metaphors
- naming rules
- "this project is / is not" statements
Keep it specific. The goal is not poetry for its own sake. The goal is to create language that helps future decisions feel easier and more coherent.
Working Loop
-
Read the project the way an outsider would. Look at the product surface, naming, docs, copy, and recurring design choices.
-
Find repeated signals. What does the project keep rewarding? What does it keep resisting? What does it make easy on purpose?
-
Turn signals into beliefs. Write down the rules the project appears to live by, and clearly label which ones are direct observation versus inference.
-
Write the lorebook in usable language. If a future builder reads it at 2am, it should help them decide what belongs.
Suggested Output Shape
BeliefsRefusalsRecurring metaphorsNaming rulesThis project is / is notWhat decisions this should make easier
Tiny Example
Beliefs: The product should feel like a workbench, not a dashboard.Refusals: It refuses to become a platform for every adjacent use case.Recurring metaphors: Tools, materials, drafts, and making.Naming rules: Prefer concrete nouns over abstract management language.This project is / is not: It is a focused studio tool, not a team operating system.
What ships with it
2 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.
- 9d ago First seen · 90 lines · 104 tokens per session scan A 720306786436
local-mythology is a skill published in the GitHub repository pyros-projects/limitless (9 stars, last pushed 26d ago), licensed MIT. It adds 104 tokens to every session and 747 once invoked, about $0.0005 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
thinking-theory-of-constraints
When throughput or latency is pipeline-limited, identify the single binding constraint and exploit, subordinate, elevate, then recheck—ignore non-constraints.
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
foundation-models
On-device LLM integration using Apple's Foundation Models framework. Use when implementing AI text generation, structured output, or tool calling.
analytics-interpretation
Interpret app metrics and make data-driven decisions. Covers DAU/MAU, retention, LTV, ARPU, App Store Connect analytics, AARRR funnel analysis, cohort analysis, and diagnostic decision trees. Use when user wants to understand their metrics, diagnose problems, or build a data-driven growth plan.
app-namer
Turn an app idea into validated, App-Store-ready name candidates. Use when the user says "name my app", "what should I call it", "app name ideas", "help me name this app", "is this name available", or needs to pick a brandable, ownable name before reserving it in App Store Connect.
in-app-events
Generates In-App Event metadata templates for App Store Connect — event names, descriptions, badge types, image specs, and deep link configuration. Use when creating events for App Store visibility, engagement campaigns, or seasonal promotions.