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 DDS-Solutions/AI-TadPole-OS --skill skillifygit clone --depth 1 https://github.com/DDS-Solutions/AI-TadPole-OSWrote 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/dds-solutions/ai-tadpole-os/skillify)<a href="https://agentmods.dev/skills/dds-solutions/ai-tadpole-os/skillify"><img src="https://agentmods.dev/badge/skills/dds-solutions/ai-tadpole-os/skillify.svg" alt="Measured on agentmods" height="20"></a>- NVIDIA SkillSpector pass
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.00037 | $0.01269 |
| Opus 5 | $0.00018 | $0.00634 |
| Sonnet 5 | $0.00007 | $0.00254 |
| Haiku 4.5 | $0.00004 | $0.00127 |
Grade A, and why
skillify 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 4d 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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
[!IMPORTANT] AI Context & Knowledge Heritage
- Subsystem: Agent Skills Registry / skillify
- Architecture:
@docs ARCHITECTURE:Documentation- Failure Path: Information drift, legacy terminology, or documentation mismatch.
- Observability: Traceability via
execution/parity_guard.py([SKILL])
Skillify — Auto-Create Skills from Workflows
Turn repetitive patterns into reusable skills. If you've done it three times, it should be a skill.
When to Skillify
✅ Good candidates:
- You've seen the user ask for the same type of work 3+ times
- A workflow involves 5+ consistent steps
- The pattern works across different projects
- Other agents could benefit from this knowledge
❌ Bad candidates:
- One-off tasks (just do them)
- Project-specific hacks (use memory instead)
- Already covered by existing skills (check first)
Skill Creation Protocol
Step 1: Identify the Pattern
What triggers this workflow? (user says X, file type Y, domain Z)
What steps are always the same?
What parts vary between uses?
What's the expected output?
Step 2: Generate SKILL.md
Skill Authoring Rules (L1/L2/L3 Progressive Disclosure Specification):
- L1 (Metadata):
nameMUST be kebab-case ($\le 64$ chars).descriptionMUST be trigger-optimized with specific action keywords ($\le 1024$ chars).- L2 (Instructions): Keep
SKILL.mdbody under 5,000 words focusing purely on procedural instructions. Use bold emphasis for non-negotiable assertions.- L3 (Resources): Offload heavy API schemas or docs to
references/, boilerplate toassets/, and fragile execution logic to deterministic scripts inscripts/.- Checkable Completion Criteria: Every step MUST end on an explicit, checkable criterion.
Use this template:
---
name: [kebab-case-name-max-64-chars]
description: [Actionable, trigger-optimized summary describing when to activate this skill, max 1024 chars]
when_to_use: "[When the user asks X, works with Y files, or Z domain. NOT for A.]"
allowed-tools: [Read, Write, Edit, Grep, Glob, Bash — only what's needed]
disable-model-invocation: true # Set to true if manually invoked only
effort: [low | medium | high]
---
# [Skill Name] — [Short Subtitle]
> [One-line philosophy or principle]
## Overview
[2-3 sentences explaining what this skill enables]
## When to Use
✅ Good for: [list]
❌ Not for: [list]
## Protocol
### Step 1: [First Action]
[Action-first instructions with **bold emphasis** on strict constraints]
### Step 2: [Second Action]
[Instructions]
### Step N: [Verification]
[Explicit, checkable completion criterion]
## Best Practices
[3-5 key rules]
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.
- 4d ago First seen · 134 lines · 37 tokens per session scan A c50cb15de303
skillify is a skill published in the GitHub repository DDS-Solutions/AI-TadPole-OS (8 stars, last pushed 2d ago), licensed MIT. It adds 37 tokens to every session and 1,269 once invoked, about $0.0002 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-09-03.
Other skills, from other repositories
anarlog
Query Anarlog meetings, notes, summaries, transcripts, participants, action items, and recurring history. Use when a user asks about their Anarlog meeting data or needs meeting context for another task.
frontend-ai-guide
Applies React/TypeScript-specific technical decision criteria, anti-pattern detection, debugging, and frontend quality gates. Use when reviewing components, hooks, browser behavior, or frontend implementation completeness.
walkeros-create-transformer
Use when creating a new walkerOS transformer to modify events in the pipeline (validate, enrich, or redact) at a before/next chain position. Example-driven workflow for the transformer interface, return values, and chaining.
dynamic-workflows
Designs and runs task-specific JavaScript harnesses with the workflow tool. Use for broad, long-running, highly structured, or adversarial work that benefits from many isolated agents: exhaustive audits, root-cause investigations, research, large triage queues, competing proposals, repeated verification, and…
subagent-orchestration
How and when to delegate work to subagents via the subagent tool (Explore, Plan, General). Use when a task involves codebase recon, implementation planning, or actual code changes that would benefit from an isolated context window instead of doing it all inline.
managing-reminders
Create and manage PostHog reminders — private, human-paced nudges that fire as in-app notifications on a schedule, optionally linked to a PostHog resource. Use when the user says "remind me to…", wants a one-off or recurring nudge (daily/weekly/monthly/yearly, a cron schedule, or a specific date/time), wants to be…