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 fredoliveira/agents --skill organize-inboxgit clone --depth 1 https://github.com/fredoliveira/agentsWrote 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/fredoliveira/agents/organize-inbox)<a href="https://agentmods.dev/skills/fredoliveira/agents/organize-inbox"><img src="https://agentmods.dev/badge/skills/fredoliveira/agents/organize-inbox/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/fredoliveira/agents/organize-inbox"><img src="https://agentmods.dev/badge/skills/fredoliveira/agents/organize-inbox.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.00021 | $0.00335 |
| Opus 5 | $0.00010 | $0.00168 |
| Sonnet 5 | $0.00004 | $0.00067 |
| Haiku 4.5 | $0.00002 | $0.00034 |
Grade A, and why
organize-inbox 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 10d 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
Inbox note organizer
Purpose
Process notes in the Inbox and file them into the appropriate folder based on their category frontmatter property.
Instructions
- List all notes in
Inbox/ - For each note, read its frontmatter
Categoryproperty - Move the note to the corresponding destination folder (see mapping below)
- If the category is missing or unclear, ask the user where the note should go
Category → Folder Mapping
| Category | Destination |
|---|---|
[[Atoms]] |
Atoms/ |
[[Ideas]] |
Ideas/ |
[[Books]] |
Reference/Books/ |
[[Meetings]] |
Reference/Meetings/ |
[[Organizations]] |
Reference/Organizations/ |
[[People]] |
Reference/People/ |
[[Places]] |
Reference/Places/ |
[[Products]] |
Reference/Products/ |
[[Recipes]] |
Reference/Recipes/ |
| (none or unrecognised) | Notes/ (confirm with user) |
Notes
- Always confirm with the user before moving notes with missing or unrecognised categories
- If a note has multiple categories, ask the user which folder takes priority
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.
- 10d ago First seen · 38 lines · 21 tokens per session scan A 9d714ed40a3d
organize-inbox is a skill published in the GitHub repository fredoliveira/agents (24 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 335 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
audit-para
Read-only PARA classification audit for the Obsidian vault, followed by an optional explicit-fix flow. Use when the user asks to audit PARA, check whether notes are in the right place, find projects missing outcomes/deadlines, or runs /audit-para.
spot-drift
Drift check for Obsidian: compare stated intentions against 30 days of vault behavior and surface verified priority gaps or avoidance questions. Use when the user asks "what am I avoiding?", "am I drifting?", "check my priorities vs behavior", "what's getting neglected?", or runs /spot-drift.
shell-env
Stow-first shell environment editing for zsh, aliases, tmux/sesh, Starship, Ghostty, yabai, Git, and dotfiles packages. Use when the user wants to add or change terminal config, aliases, shell startup, or Stow-managed symlinks. Route Neovim-specific work to neovim and whole-system health checks to audit.
til
TIL capture for explicit requests to save learned material from a session into an engaging Obsidian note. Use when the user runs /til or asks to save, document, or write up what they learned.
goals
Obsidian goals review for quarterly or monthly goal notes. Use when the user asks to review goals, run an OKR check-in, update goals, set monthly or quarterly goals, check whether goals are on track, or runs /goals.
maintain
Runs a read-only health check on the Obsidian vault — finds broken links, orphaned notes, tag inconsistencies, and wiki issues, then reports prioritized fixes. Make sure to use this skill whenever the user says "vault health check", "fix broken links", "clean up my vault", "vault maintenance", or runs /maintain. Never…