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 codies-researchgit 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/codies-research)<a href="https://agentmods.dev/skills/pyros-projects/limitless/codies-research"><img src="https://agentmods.dev/badge/skills/pyros-projects/limitless/codies-research.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.00091 | $0.00894 |
| Opus 5 | $0.00046 | $0.00447 |
| Sonnet 5 | $0.00018 | $0.00179 |
| Haiku 4.5 | $0.00009 | $0.00089 |
Grade A, and why
codies-research 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 — 130 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Codies Research
Overview
This skill turns Codie into a research operator.
It is for real research work, not planning theater:
- gather current evidence fast
- rank sources while collecting them
- resolve contradictions instead of averaging them together
- answer directly
- then offer strong next directions for deeper research
This skill is host-native first.
Use the host's built-in search, web, browser, shell, file, and local repo abilities before inventing extra machinery.
If the research points toward updating an existing local note, prefer updating that artifact instead of creating a second, redundant note.
When To Use
Use this skill when the user wants:
- current facts or recent changes
- source-backed research with links
- technical/library/framework comparisons
- verification of whether something is actually true
- an update to an existing local research note
- deeper follow-up branches after an initial answer
Do not use this skill for:
- pure brainstorming with no evidence requirement
- rewriting text the user already provided
- coding tasks that do not need research
Default Posture
- Do the research immediately unless ambiguity is materially risky.
- Prefer primary and official sources when available.
- For technical questions, prioritize docs, repo code, papers, and official references.
- For current or unstable topics, verify with live sources.
- Distinguish observed fact, quoted claim, inference, and uncertainty.
- Answer first. Notes and extras come second.
Operator Loop
-
Scope quickly. Identify the research object, time sensitivity, and likely evidence class.
-
Acquire sources immediately. Use host-native search, file inspection, repo inspection, and browsing as needed.
-
Grade sources while collecting. Track:
- primary vs secondary
- current vs stale
- evidence vs marketing
- direct statement vs inference
-
Resolve contradictions. Prefer stronger evidence. If uncertainty remains, say so explicitly.
What ships with it
4 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.
- 8d ago First seen · 130 lines · 91 tokens per session scan A 1dba19cd64f6
codies-research is a skill published in the GitHub repository pyros-projects/limitless (9 stars, last pushed 25d ago), licensed MIT. It adds 91 tokens to every session and 894 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.