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 kairyou/agent-tools --skill at-daily-loggit clone --depth 1 https://github.com/kairyou/agent-toolsWrote 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/kairyou/agent-tools/at-daily-log)<a href="https://agentmods.dev/skills/kairyou/agent-tools/at-daily-log"><img src="https://agentmods.dev/badge/skills/kairyou/agent-tools/at-daily-log/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/kairyou/agent-tools/at-daily-log"><img src="https://agentmods.dev/badge/skills/kairyou/agent-tools/at-daily-log.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 26 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Rogue Agent · line 62 Skill establishes unauthorized persistence across sessions via cron jobs, startup scripts, or state files. Session persistence allows an attacker to maintain access beyond the current interaction.Fix: Remove any persistence mechanisms (cron jobs, startup scripts, state files). Skills should not maintain state across sessions without explicit user consent.
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.00048 | $0.01882 |
| Opus 5.5 | $0.00019 | $0.00753 |
| Sonnet 5.5 | $0.00010 | $0.00376 |
| Haiku 4.5 | $0.00005 | $0.00188 |
Grade A, and why
at-daily-log 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 — 143 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Daily Work Log
resolve evidence -> group related commits -> draft or record
Date and evidence scope
Default to today. Accept plain-language dates or ranges (2026-07-31, yesterday, last
week, this month) and normalize to [from, to]; query through <to + 1 day> because
Git's --until boundary is exclusive. State the resolved date or range.
Read optional workProjects from ~/.agent-tools/config.jsonc. An entry is a path
or { "path", "prompt" }, where the prompt is free text this skill follows for that
project, such as how to label items or which commits to skip.
- No project named: current Git repository plus configured projects.
- Projects named directly: only those projects.
- "Also include" /
另外包含: add them to the default scope.
Resolve paths to Git roots and deduplicate them. Report invalid paths; a non-Git current directory does not block other valid projects. Do not clone remote URLs without consent.
For each repository, resolve the author with git -C <root> config user.name; never
infer aliases or use the remote login as the author.
Inspect all local branches, current HEAD, user-named branches, and configured
upstreams. Unless the user requests local-only data, refresh only the configured
upstream branches, grouped into one best-effort git fetch --no-tags <remote> <branch...> per involved remote. Fetch failure is non-fatal. Do not change the
working tree or local branch history.
Then list candidates with git -C <root> log --no-merges --since=<from> --until=<to+1day> --format=%H%x09%an --branches HEAD <upstream refs>, taking the
upstream refs from git -C <root> for-each-ref --format=%(upstream) refs/heads/.
Passing no ref walks only the current branch, so work on an unmerged branch reads as
no activity; --all reaches past the scope above into remote branches nobody tracks.
Keep the rows whose %an equals the resolved name exactly. Never pass --author: it
matches the whole Name <email> header, so anchored patterns silently match nothing.
When the window holds commits but none carry that name, report the names actually
found instead. Deduplicate commits by hash.
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 · 143 lines · 48 tokens per session scan A d25a18281c3c
at-daily-log is a skill published in the GitHub repository kairyou/agent-tools (181 stars, last pushed 3d ago), licensed MIT. It adds 48 tokens to every session and 1,882 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
cmux-testing
Choose scoped cmux verification, add behavioral tests, and validate Swift test targets and wiring. Use when adding tests or deciding what local/CI evidence a change needs.
git-workflow
Automate the complete Git development workflow — create feature branches with conventional naming, atomic commits with conventional commit messages, interactive rebase, squash merges, PR body generation from commit history, branch cleanup, and git worktree patterns. Use when user asks to create a branch, commit…
git-master
Advanced Git operations — rebase, squash, fixup, blame, bisect, reflog, code archaeology (git log -S/-G), worktrees. Use when the task mentions rebase, squash, bisect, blame, reflog, fixup, finding deleted code, tracing commit history, cleaning up a branch, or recovering lost work.
to-tickets
A workflow for turning a written plan or specification into separate GitHub issues, with each issue covering one independently finishable piece of work.
github-publish-changes
Publish intentional local changes by confirming scope, creating a branch when needed, staging selected files, committing, pushing, and creating a Draft Pull Request through the connected GitHub service.
address-pr-feedback
Unified PR feedback workflow - collect, triage, and fix review comments in a single command.