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 agentmods add skills/daloopa/investing/meta-skillnpx skills add daloopa/investing --skill meta-skillgit clone --depth 1 https://github.com/daloopa/investingWrote 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/daloopa/investing/meta-skill)<a href="https://agentmods.dev/skills/daloopa/investing/meta-skill"><img src="https://agentmods.dev/badge/skills/daloopa/investing/meta-skill.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.00000 | $0.04693 |
| Opus 5 | $0.00000 | $0.02346 |
| Sonnet 5 | $0.00000 | $0.00939 |
| Haiku 4.5 | $0.00000 | $0.00469 |
Grade A, and why
meta-skill 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 6d 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 — 312 lines — stays where its author put it; the contents beside it link to each section on GitHub.
| name | description | argument-hint |
|---|---|---|
| convert-skills-to-prompts | Convert all Claude Code skills into MCP prompt functions | (none) |
Convert every skill in .claude/skills/ into a Python MCP prompt function, producing a single output file prompts.py with one @daloopa_mcp.prompt function per skill.
This is a conversion task, not a rewrite. The analytical logic, calculations, data requirements, and output structure of each skill must be preserved exactly. What changes is the execution context: from Claude Code (file system, local scripts, MCP tools) to MCP prompt (MCP tools only, no file system, no local scripts).
Step 0: Read All Source Files
Read these files first — you need them all loaded before you start converting:
-
Shared references:
.claude/skills/data-access.md— data access patterns, tool signatures, citation rules.claude/skills/design-system.md— formatting, analytical voice, HTML template, color palette
-
Every skill file:
.claude/skills/*/SKILL.md— read all of them
-
Note the full skill list from the directory listing. Some skills may reference other skills (e.g.,
/initiatecalls/research-note+/build-model,/updatereferences prior output). Capture these dependencies.
Step 1: Understand the Two Shared References
Before converting any skill, analyze data-access.md and design-system.md to build a dependency map. Each skill uses different parts of these files.
data-access.md — Section Inventory
Identify these sections and what each provides:
| Section | Content | MCP Prompt Relevance |
|---|---|---|
| Section 1: Daloopa MCP Tools | Tool signatures: discover_companies, discover_company_series, get_company_fundamentals, search_documents |
ALWAYS INLINE — every skill needs these |
| Section 1: API Script Fallback | python recipes/company_fundamentals.py etc. |
ALWAYS DROP — no file system in MCP prompt context |
| Section 2: External Market Data | Stock quotes, trading multiples, historical prices, peer multiples, risk-free rate | CONDITIONAL — only inline for skills that use market data |
| Section 2: Market Data Resolution Order | MCP → infra scripts → web search → defaults | ALWAYS INLINE — preserve the full 4-step resolution order (MCP tools → infra scripts → web search → defaults) |
| Section 3: Consensus Estimates | Consensus revenue/EPS, forward estimates, revisions, price targets | CONDITIONAL — only inline if the skill doesn't already handle consensus in its own steps |
| Section 4: Citation Requirements | Daloopa citation format, fundamental_id linking, document citations | ALWAYS INLINE — mandatory for all skills |
| Section 5: Infrastructure Tools | market_data.py, chart_generator.py, projection_engine.py, excel_builder.py, docx_renderer.py, etc. | ALWAYS DROP — not available in MCP prompt context |
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.
- 6d ago First seen · 312 lines · 0 tokens per session scan A abd4a02c2626
meta-skill is a skill published in the GitHub repository daloopa/investing (487 stars, last pushed 1mo ago), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 4,693 tokens. 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-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…