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 agentproto/ts --skill ap-appsgit clone --depth 1 https://github.com/agentproto/tsWrote 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/agentproto/ts/ap-apps)<a href="https://agentmods.dev/skills/agentproto/ts/ap-apps"><img src="https://agentmods.dev/badge/skills/agentproto/ts/ap-apps/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/agentproto/ts/ap-apps"><img src="https://agentmods.dev/badge/skills/agentproto/ts/ap-apps.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.00075 | $0.01005 |
| Opus 5.5 | $0.00030 | $0.00402 |
| Sonnet 5.5 | $0.00015 | $0.00201 |
| Haiku 4.5 | $0.00007 | $0.00101 |
Grade A, and why
ap-apps 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 17d 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 — 74 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ap-apps
When to use
- An app bundle (
.agentproto/APP.md— agents + WORKFLOW.md files) needs installing, applying to a scope, or running. - You must run an app's agents one-at-a-time (scout → tailor pipelines) or all at once.
- You need to read/write an app's scoped data or fetch its artifact/skill content.
Install → apply → run
// 1. Install from the emitted app directory (validates ALL WORKFLOW.md tool ids up front)
app_install({ "dir": "/path/to/app" })
// → { "appId": "@agentproto/code-team", ... }
// 2. Apply to a scope (default 'root') — makes its capabilities available there
app_apply({ "appId": "@agentproto/code-team" })
// 3. Run: all agents concurrently (default)
app_run({ "appId": "@agentproto/code-team", "prompt": "Review the auth module" })
// ...or one-at-a-time in order — each waits for the previous to finish
app_run({ "appId": "@agentproto/scout-tailor",
"sequence": ["scout", "tailor"] })
// 4. Poll / stop
app_status({ "appRunId": "run_..." }) // live session descriptors + workflow runs
app_stop({ "appRunId": "run_..." }) // kills every session in the run, marks ended
app_install validates every WORKFLOW.md tool id against the daemon's dispatchable tools all at once — you get the full missing-id list, not one failure at a time. Re-installing the same appId upserts. The mastra-agent adapter must resolve for agent steps.
Catalog, artifacts, data
app_catalog({}) // browsable apps merged with install status
app_list({}) // installed apps + run history
app_artifact_get({ "appId": "..." }) // artifact HTML (daemon exposes it, host writes it)
app_skill_get({ "appId": "..." }) // skill files (utf-8; binaries skipped with a warning)
app_data_list({ "appId": "...", "dir": "data/jobs" }) // entries under the app dir
app_data_read({ "appId": "...", "path": "data/state.json" })
app_data_write({ "appId": "...", "path": "data/state.json", "content": { "ok": true } })
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.
- 17d ago Changed f366c290c859
- 1mo ago First seen · 74 lines · 75 tokens per session scan A 84e98dbfe360
ap-apps is a skill published in the GitHub repository agentproto/ts (10 stars, last pushed yesterday), licensed Apache-2.0. It adds 75 tokens to every session and 1,005 once invoked, about $0.0003 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-09-04.
Other skills, from other repositories
skill-creator-primer
You MUST load this skill before the skill-creator skill AND before making ANY change to, or conducting a review of ANY Agent Skill. Triggers include creating, editing, reviewing, or contributing to any part of an Agent Skill (description, frontmatter, body, references, scripts, trigger evals, conflicts, etc).
llm-wiki
Use when building or maintaining a self-contained personal knowledge base (an LLM wiki) in plain markdown. Triggers: ingesting sources into a wiki, querying wiki knowledge, linting wiki health, auditing article claims against their sources, critiquing a wiki source's reasoning, superseding stale knowledge, 'add to…
extract-wisdom
Extract wisdom, insights, and actionable takeaways from YouTube videos, blog posts, articles, or text files. Use when asked to extract wisdom or key insights from a given content source.
apply-mantel-styles
Provides guidelines for applying Mantel's brand styles to diagrams and frontend components. Use when asked to create visuals that need to align with Mantel's branding.
home-assistant
This skill should be used when helping with Home Assistant setup, including creating automations, modifying dashboards, checking entity states, debugging automations, and managing the smart home configuration. Use this for queries about HA entities, YAML automation/dashboard generation, or troubleshooting HA issues.
deepeval
Use when discussing or working with DeepEval (the python AI evaluation framework).