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 Mark393295827/third-brain-v7-skills --skill daily-okrgit clone --depth 1 https://github.com/Mark393295827/third-brain-v7-skillsWrote 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/mark393295827/third-brain-v7-skills/daily-okr)<a href="https://agentmods.dev/skills/mark393295827/third-brain-v7-skills/daily-okr"><img src="https://agentmods.dev/badge/skills/mark393295827/third-brain-v7-skills/daily-okr/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/mark393295827/third-brain-v7-skills/daily-okr"><img src="https://agentmods.dev/badge/skills/mark393295827/third-brain-v7-skills/daily-okr.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00031 | $0.00932 |
| Opus 5.5 | $0.00012 | $0.00373 |
| Sonnet 5.5 | $0.00006 | $0.00186 |
| Haiku 4.5 | $0.00003 | $0.00093 |
Grade A, and why
daily-okr 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 — 101 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily OKR
<skill_contract> Date, one priority objective, available time, active project, current inputs, and prior-day evidence. A seven-KR daily cycle linking input, cognition, wiki, behavior, creativity, output, and feedback. Each claimed KR has a durable receipt, and today's feedback changes one explicit next-day action or knowledge state. <non_goals>Seven unrelated priorities, invented completion, activity counting without evidence, or treating scheduled notes as execution.</non_goals>
Run one daily objective through seven linked Key Results. The cycle compounds only when evidence from today changes tomorrow's behavior or knowledge state.
Usage Template
Provide: date, one objective, available time, active project, knowledge inputs, and yesterday's evidence. Optional: a scheduled knowledge-loop note; treat it as input, not proof of execution.
Workflow
- Load the current daily state and any scheduled-loop proposal.
- Choose one objective tied to an active project or explicit learning goal.
- Set a total time budget and a minimum viable day.
- Carry forward only unresolved items with an owner or decision value.
<unknowns_gate>
If priority, available time, or completion evidence is missing, return NEEDS_INPUT with one narrow probe. If the day is constrained, select the minimum cycle rather than fabricating seven completed results.
</unknowns_gate>
Create seven causally linked KRs:
- Input: capture one high-value source or observation.
- Cognition: extract one mechanism, contradiction, or decision implication.
- Wiki: write or improve one durable note with provenance.
- Behavior: execute one minimum behavior linked to the objective.
- Creativity: produce one alternative or falsifiable experiment.
- Output: ship one reviewable artifact or project increment.
- Feedback: record evidence, error, and tomorrow's adjustment.
Each KR needs an artifact or receipt. Keep unfinished work visible; do not convert a scheduled trigger into a success claim.
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 · 101 lines · 31 tokens per session scan A 517b79ee8be1
daily-okr is a skill published in the GitHub repository Mark393295827/third-brain-v7-skills (141 stars, last pushed 1mo ago), licensed MIT. It adds 31 tokens to every session and 932 once invoked, about $0.0001 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
obsidian-ai-setup
Bootstrap an Obsidian vault with the AI Pro Obsidian Plugin. Creates the complete vault structure, system files, Obsidian configuration, memory system, hooks, and output styles, then runs personalized onboarding to tailor the workspace to the user. Uses a single universal structure with no mode selection. Trigger when…
apply
A browser-based job application workflow for submitting applications through services such as Ashby, Greenhouse, Lever, and Hacker News. It uses prepared candidate information, answers, job links, and cover letters.
screenpipe-api
Query the user's local and synced-device data via the screenpipe REST API at localhost:3030 — recordings, audio, UI, meetings, connected services, and memory. Use for screen activity, other-device or cross-device history, productivity, media export, connections, durable memory, or discovering and automating saved…
retro-lost
Run a retrospective for an abandoned agent session (untouched for over 24 hours, never closed with a retro): rebuild context cold from the transcript, list what was built, sort Keep/Drop/Try and file the durable parts. Use from a nightly routine or on demand. Triggers: /retro-lost, retro for an abandoned session.
pkm-session-end
Use when wrapping up a work session — creates devlog entry, captures undocumented decisions/research/debugging, audits link health of session work, and updates project index. Primarily used via the pkm-capture agent.
nsr
A routine for starting a new, visible coding-agent session automatically through a scheduled task, so it appears in the recent-session list without someone pressing a start button.