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 donegit 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/done)<a href="https://agentmods.dev/skills/fredoliveira/agents/done"><img src="https://agentmods.dev/badge/skills/fredoliveira/agents/done/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/done"><img src="https://agentmods.dev/badge/skills/fredoliveira/agents/done.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.00044 | $0.00788 |
| Opus 5.5 | $0.00018 | $0.00315 |
| Sonnet 5.5 | $0.00009 | $0.00158 |
| Haiku 4.5 | $0.00004 | $0.00079 |
Grade A, and why
done 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.
How it starts
The opening of the file, as written. The whole thing — 89 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Summarize this Claude Code session, create a dedicated session note in Obsidian, and link it from today's daily note.
Instructions
- Review the full conversation history for this session.
- Come up with a short summary title (2-6 words, no date) describing the overall theme.
- Write a detailed session note in markdown. The note MUST begin with YAML frontmatter and then use the sections described below. Skip any sections that don't make sense. The only non-negotiable is the frontmatter, which must always be present. Use this template:
---
created: YYYY-MM-DD
project: <working directory name or repo name>
harness: <who you are ('claude-code', or 'codex', or 'pi', etc)>
tags:
- note/agent-session
---
# <summary title>
## Summary
<1-3 sentence overview of the session>
## What was done
- <bullet list of key actions, changes, and outcomes>
## Decisions made
- <bullet list of decisions and the reasoning behind them>
- <include trade-offs considered, alternatives rejected, and why>
## Relevant code snippets
<relevant new commands that were created, code snippets that were mentioned, etc>
## File changes
- `path/to/file` -- <what changed and why>
- <list every file that was created, modified, or deleted>
## Deferred / Postponed
- <anything discussed but intentionally left for later>
- <known issues discovered but not addressed>
- <if nothing was deferred, write "None">
## Notes
- <any additional context, gotchas, or follow-up items>
- <if $ARGUMENTS was provided, incorporate that context here or in the relevant section above>
Be thorough -- err on the side of detail. The goal is a complete record of the session.
4. Get today's date in YYYY-MM-DD format and construct the note path:
Reference/Agent Sessions/YYYY-MM-DD <summary title>
5. Find the full path to the Obsidian vault by running obsidian vault - the path will be listed.
5. Create the session note file at /Reference/Agent Sessions/YYYY-MM-DD .md
6. Append a link to the session note in today's daily note by running:
obsidian daily:append content="- [[YYYY-MM-DD <summary title>]]" silent
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 · 89 lines · 44 tokens per session scan A 2bc9d6cb6098
done is a skill published in the GitHub repository fredoliveira/agents (25 stars, last pushed 4mo ago), licensed MIT. It adds 44 tokens to every session and 788 once invoked, about $0.0002 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-30.
Other skills, from other repositories
todays-focus
Choose three meaningful focus areas for today using current tools and personal vault context, with a check-in, three journal prompts, and optional saving of the full reflection.
close-day
Review today's log and meeting notes, optionally import Granola meetings, propose Atomic Notes, and suggest next-day actions.
shell-env
Edit the Stow-managed shell and terminal environment in /.dotfiles/home, including zsh, aliases, tmux/sesh, Starship, Ghostty, yabai, Git, and link structure. Use for focused terminal configuration changes. Route Neovim work to neovim and whole-system health checks to audit.
til
Save demonstrated learning, corrected misconceptions, and useful examples from a session as a durable Obsidian TIL note. Use when a learning workflow hands off a session or the user asks to save what they learned.
standup
Draft a concise daily standup from Git evidence and user-provided non-code work. Use for standups, daily updates, or summaries of the requested work period.
tfw-daily-task
Complete a bounded everyday request after project and purpose checks, preserving selected Trace and a checked result without a second planning approval.