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 eugenepyvovarov/mcpbundler-agent-skills-marketplace --skill things3-agent-skillgit clone --depth 1 https://github.com/eugenepyvovarov/mcpbundler-agent-skills-marketplaceWrote 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/eugenepyvovarov/mcpbundler-agent-skills-marketplace/things3-agent-skill)<a href="https://agentmods.dev/skills/eugenepyvovarov/mcpbundler-agent-skills-marketplace/things3-agent-skill"><img src="https://agentmods.dev/badge/skills/eugenepyvovarov/mcpbundler-agent-skills-marketplace/things3-agent-skill/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/eugenepyvovarov/mcpbundler-agent-skills-marketplace/things3-agent-skill"><img src="https://agentmods.dev/badge/skills/eugenepyvovarov/mcpbundler-agent-skills-marketplace/things3-agent-skill.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.00073 | $0.00791 |
| Opus 5.5 | $0.00029 | $0.00316 |
| Sonnet 5.5 | $0.00015 | $0.00158 |
| Haiku 4.5 | $0.00007 | $0.00079 |
Grade A, and why
things3-manager 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.
This is a copy
100% identical to things3-manager — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 50 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Things 3 Manager (CLI)
Quick start
- Ensure Things 3 is installed and opened at least once.
- In Things → Settings → General: enable “Enable Things URLs”.
- Run the CLI (auto-bootstraps
.skills-data/things3-manager/venvand installs deps on first run):bash .codex/skills/things3-manager/scripts/things --helpbash .codex/skills/things3-manager/scripts/things inboxbash .codex/skills/things3-manager/scripts/things search "weekly review"bash .codex/skills/things3-manager/scripts/things add-todo --title "Book flights" --when today --tag travel --checklist "passport" --checklist "charger"
Operating rules (for Codex)
- Prefer read-only commands first (
inbox,today,search,projects,areas,tags) to discover UUIDs and current state. - Before any write command (
add-todo,add-project,update-todo,update-project), summarize the exact changes and confirm with the user. - If the user provides a project/area/heading by name, resolve it by listing (
projects/areas/headings) before writing.
Local data and env
- Store all mutable state under <project_root>/.skills-data//.
- Keep config and registries in .skills-data// (for example: config.json, .json).
- Use .skills-data//.env for SKILL_ROOT, SKILL_DATA_DIR, and any per-skill env keys.
- Install local tools into .skills-data//bin and prepend it to PATH when needed.
- Install dependencies under .skills-data//venv:
- Python: .skills-data//venv/python
- Node: .skills-data//venv/node_modules
- Go: .skills-data//venv/go (modcache, gocache)
- PHP: .skills-data//venv/php (cache, vendor)
- Write logs/cache/tmp under .skills-data//logs, .skills-data//cache, .skills-data//tmp.
- Keep automation in /scripts and read SKILL_DATA_DIR (default to <project_root>/.skills-data//).
- Do not write outside and <project_root>/.skills-data// unless the user requests it.
What ships with it
7 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.
- 1mo ago First seen · 50 lines · 73 tokens per session scan A 96f2f47ddf1b
things3-manager is a skill published in the GitHub repository eugenepyvovarov/mcpbundler-agent-skills-marketplace (11 stars, last pushed 8mo ago), licensed MIT. It adds 73 tokens to every session and 791 once invoked, about $0.0003 per session on Opus 5.5. A static security scan graded it A with 0 findings. It is 100% identical to things3-manager, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
wayfinder
A planning method that maps a large, uncertain project into linked decision tickets in a repository's issue tracker. An issue tracker is a system for recording and organizing project work.
triage
A process for reviewing issues and outside pull requests through category and status labels. An issue is a recorded problem or request, while a pull request is a proposed code change for review.
meeting-notes
Estructura y formatea notas de reunión siguiendo las mejores prácticas de PM. Úsalo cuando te pidan crear notas de reunión, formatear notas de discusión, capturar elementos de acción, o documentar decisiones de cualquier tipo de reunión. Produce notas estructuradas con decisiones, elementos de acción (responsable +…
technical-debt-register
Documenta y prioriza un backlog de deuda técnica con impacto empresarial, estimaciones de esfuerzo y estrategia de resolución. Úsalo cuando se te pida auditar deuda técnica, crear un registro de deuda, priorizar deuda técnica para un trimestre, documentar atajos arquitectónicos o construir una hoja de ruta de…
to-tickets
A method for turning a plan, specification, or conversation into small tickets, where each ticket is a complete vertical slice of work and lists the tickets that must come first.
cs-health-scorecard
Construir un cuadro de mando de salud del cliente para una cuenta específica. Úsalo cuando te pidan calificar la salud de la cuenta, evaluar el riesgo de renovación, construir un panel de salud o evaluar la probabilidad de que una cuenta se renueve o expanda. Produce un cuadro de mando de salud estructurado con estado…