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 MSApps-Mobile/claude-plugins --skill dogit clone --depth 1 https://github.com/MSApps-Mobile/claude-pluginsWrote 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/msapps-mobile/claude-plugins/do)<a href="https://agentmods.dev/skills/msapps-mobile/claude-plugins/do"><img src="https://agentmods.dev/badge/skills/msapps-mobile/claude-plugins/do/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/msapps-mobile/claude-plugins/do"><img src="https://agentmods.dev/badge/skills/msapps-mobile/claude-plugins/do.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.00092 | $0.00575 |
| Opus 5.5 | $0.00037 | $0.00230 |
| Sonnet 5.5 | $0.00018 | $0.00115 |
| Haiku 4.5 | $0.00009 | $0.00057 |
Grade A, and why
do 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.
What it actually says
do: Memory-Aware Task Execution
Every task you run should start from what you know, not from zero.
Execution Workflow
Before you start: Load context
# What's already done / decided related to this task?
COWORK_MEM_DB=~/mnt/.claude/.cowork-mem/memory.db \
python3 {SKILL_DIR}/scripts/vector_search.py "<task description>" --limit 8
# Any relevant errors or blockers?
python3 {SKILL_DIR}/scripts/memory_store.py search "<key term>" --type error --limit 5
Use the recalled context to:
- Skip work that's already done
- Avoid approaches that previously failed (check errors)
- Follow established patterns (check past decisions)
- Build on existing file structure (check file_edits)
During execution: Save what matters
As you work, save observations for significant actions:
# When you make a choice
python3 {SKILL_DIR}/scripts/memory_store.py add decision \
"<what you chose and why>" --tags "<task-tag>"
# When you discover something non-obvious
python3 {SKILL_DIR}/scripts/memory_store.py add insight \
"<what you learned>" --tags "<task-tag>"
# When you hit an error and solve it
python3 {SKILL_DIR}/scripts/memory_store.py add error \
"<error encountered + solution>" --tags "<task-tag>"
Don't over-log. Save things future-you would want to know that aren't obvious from the code.
After completion: Close the loop
python3 {SKILL_DIR}/scripts/memory_store.py add note \
"Completed: <what was done>. Status: <done/partial>. Next: <what remains>" \
--tags "completed,<task-tag>"
Parallelism with PostToolUse Hook
If the PostToolUse hook is active, file edits and bash commands are captured automatically. Focus your manual saves on:
- Decisions (why you chose this approach)
- Insights (non-obvious things you discovered)
- Errors (problems and solutions)
The hook handles the "what happened"; you handle the "why it matters."
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 · 69 lines · 92 tokens per session scan A 3d37ba9887e4
do is a skill published in the GitHub repository MSApps-Mobile/claude-plugins (10 stars, last pushed today), licensed MIT. It adds 92 tokens to every session and 575 once invoked, about $0.0004 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
decision
Full decision lifecycle in Semantica — record, query, find precedents (hybrid/advanced), analyze influence, explain, insights dashboard, list, and record exceptions. Uses AgentContext, ContextGraph, DecisionQuery, CausalChainAnalyzer, DecisionRecorder.
session-handoff
Synthesizes the current session into a structured HANDOFF block for context transfer between sessions. Captures what was built, decisions made, and unresolved items.
optimizer
Framework-driven audit and optimizer for a Baalda vault. Applies 10 frameworks covering CLAUDE.md quality, wiki structure, compression, context rot, memory, progressive disclosure, hygiene, cross-file synthesis, architecture and discoverability, plus F10 Claude 5 rule rewriting. Every finding ships a concrete fix; the…
agentic-os-obsidian
Set up an agentic OS inside an Obsidian vault — a configurable command-center dashboard with 5 auto-installed, bundled plugins (Dataview, CustomJS, Shell-commands, Terminal, Homepage), Home + per-profile + Vault Overview pages, KPI cards, sparklines, heatmap, task rollup, and a button bar wired to user-defined Claude…
operator
Build and schedule a personalized Operator prompt that runs a Baalda vault as a second brain on a recurring cadence. Run it from inside the vault: it reads Context/ and CLAUDE.md first to infer org, team, brand voice and paths, then asks only the gaps (cadence, connectors, DM recipient, budgets, signature), writes the…
skill-os-builder
Stand up a self-contained second-brain "OS" that lives entirely inside a Claude skill — a short SKILL.md router plus context files, no vault, cloud, or MCP server. Use when the user says "set up a skill OS", "build my second brain as a skill", "skill OS", or wants the simplest portable AI OS.