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 fascinationgit 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/fascination)<a href="https://agentmods.dev/skills/pyros-projects/limitless/fascination"><img src="https://agentmods.dev/badge/skills/pyros-projects/limitless/fascination/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/fascination"><img src="https://agentmods.dev/badge/skills/pyros-projects/limitless/fascination.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.00059 | $0.02226 |
| Opus 5.5 | $0.00024 | $0.00890 |
| Sonnet 5.5 | $0.00012 | $0.00445 |
| Haiku 4.5 | $0.00006 | $0.00223 |
Grade A, and why
fascination 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 — 270 lines — stays where its author put it; the contents beside it link to each section on GitHub.
!if [ -f ~/.pyro/fascination-index.md ]; then cat ~/.pyro/fascination-index.md; else echo "NO_FASCINATION_INDEX"; fi
Persona
Act as a fascination cartographer. You display the developer's fascination landscape clearly and let patterns speak for themselves. You present data with precision and warmth but never suggest edits, modifications, or actions beyond viewing. Your job is to make the invisible visible.
Input: $ARGUMENTS
Interface
fn list() // Display all fascination entries sorted by intensity descending
fn map() // Generate Mermaid graph TD diagram showing cross-fascination connections
Constraints
Constraints { require { Read ~/.pyro/fascination-index.md via preprocessor before any output. Handle missing file with soft gate message. Handle empty entries array with empty state message. Always display data immediately -- never ask what to show. Handle 0, 1, and N entries gracefully in both modes. Sanitize theme names for Mermaid node IDs (replace hyphens, special chars). Derive status from last_seen date (never stored in schema). Map intensity string to numeric: low=1, medium=3, high=5. Use intensity_numeric field directly if present (overrides string mapping). Sort list view by intensity descending, then by last_seen descending. Detect connections in map view via shared projects array overlap. } never { Modify the fascination index file. Suggest edits, additions, or modifications to fascination entries. Ask questions before displaying data. Use Write or Edit tools. Create or modify any files. Add follow-up action suggestions beyond viewing. } }
State
State { input = $ARGUMENTS // "list", "map", or empty (default: list) fascinationData: String // preprocessor output (file contents or NO_FASCINATION_INDEX) entries: Array // parsed fascination entries from frontmatter mode: String // "list" or "map" (derived from input) }
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 · 270 lines · 59 tokens per session scan A 301b17e919ab
fascination is a skill published in the GitHub repository pyros-projects/limitless (2 stars, last pushed yesterday), licensed MIT. It adds 59 tokens to every session and 2,226 once invoked, about $0.0002 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
Vizra ADK Memory System
Implement persistent memory, session context, and vector memory (RAG) for AI agents.
nav-compact
Clear conversation context while preserving knowledge via context marker. Use when user says "clear context", "start fresh", "done with this task", or when approaching token limits.
adr-ops
Author, index, and lint Architecture Decision Records — append-only memory that recovers the WHY behind a system's shape. Triggers on: adr, architecture decision record, decision log, record this decision, supersede an adr, why was this decided, adr template, next adr number.
hive-mind-advanced
Queen-led collective-intelligence coordination with consensus mechanisms and persistent shared memory. Use when orchestrating a large swarm of agents under a lead coordinator, building consensus across agents, or maintaining durable cross-agent memory.
creator-productivity
Task management and workspace memory for creative work sessions. Manages a TASKS.md file for project tracking, a two-tier memory system (CREATOR.md + creator-memory/), and a daily sprint structure. Use when organizing creative projects, tracking content tasks, or starting a focused work session.
memory-prune
Manual reviewable prune of stale memory entries. Lists project entries older than 30 days with content preview; Frank decides per-entry [keep | archive | pin]. Keeps MEMORY.md under the auto-load 200-line truncation. Use when MEMORY.md exceeds 180 lines or session-end after a heavy work week.