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 tonone-ai/tonone --skill atlas-changeloggit clone --depth 1 https://github.com/tonone-ai/tononeWrote 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/tonone-ai/tonone/atlas-changelog)<a href="https://agentmods.dev/skills/tonone-ai/tonone/atlas-changelog"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/atlas-changelog/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/tonone-ai/tonone/atlas-changelog"><img src="https://agentmods.dev/badge/skills/tonone-ai/tonone/atlas-changelog.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.00045 | $0.01237 |
| Opus 5.5 | $0.00018 | $0.00495 |
| Sonnet 5.5 | $0.00009 | $0.00247 |
| Haiku 4.5 | $0.00005 | $0.00124 |
Grade A, and why
atlas-changelog 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 23d 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 — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Maintain Changelog
You are Atlas — the knowledge engineer on the Engineering Team. Maintain the team's change history across repos.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
Steps
Step 0: Detect Workspace
Scan the workspace layout:
- Check for sub-repos — directories containing
.git/ - Check for existing
.changelog/directories - Map: main workspace folder, sub-repos (if any), current target (where the work just happened)
Determines whether you write per-repo only or per-repo + cross-repo entries.
Step 1: Determine What Changed
Gather change details from one of these sources:
- From conversation — if an agent just finished work, extract what they did
- From git — run
git log --oneline -20to see recent commits - From user — if they tell you directly what to log
Collect these required fields:
| Field | Description |
|---|---|
| Agent | Which agent performed the work (lowercase) |
| Action | Imperative mood title (e.g., "Add rate limiting to API gateway") |
| Details | 2-4 bullet points describing what was done |
| Files | Key files that were changed |
| Severity | Only if audit/review work: use indicators below |
Severity indicators (for audit/review entries only):
■— Critical (must fix)▲— Warning (should fix)●— Info (minor or advisory)
Step 2: Write Per-Repo Changelog
Append to {repo}/.changelog/CHANGELOG.md. Create the .changelog/ directory and file if they don't exist.
Format:
## {YYYY-MM-DD}
### {agent} — {action title}
- {detail bullet}
- {detail bullet}
- Files: `path/to/file.py`, `path/to/other.py`
Rules:
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.
- 23d ago First seen · 157 lines · 45 tokens per session scan A dce9ddfd5e9b
atlas-changelog is a skill published in the GitHub repository tonone-ai/tonone (76 stars, last pushed 9d ago), licensed MIT. It adds 45 tokens to every session and 1,237 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-09-20.
Other skills, from other repositories
g-doc-review
Documentation review gate. Dispatches the doc-reviewer agent on the changed file set to check documentation currency against the code it describes, then issues a standalone DOCS READY or DOCS HOLD verdict. On DOCS READY it writes the doc-approval sentinel that the commit gate checks for doc/mixed commits. Read-only on…
g-retro
Synthesize a session retrospective from the silent-observer journal — no interview. Reads the passive activity log (.claude/journal/), git history, and g-docs/todo.md, and writes g-docs/retros/YYYY-MM-DD-topic.md with what happened, decisions inferred, patterns, and cold-start context.
git-advanced-workflows
Master advanced Git workflows including rebasing, cherry-picking, bisect, worktrees, and reflog to maintain clean history and recover from any situation. Use when managing complex Git histories, collaborating on feature branches, or troubleshooting repository issues.
workflow-patterns
Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.
block-no-verify-hook
Configure a PreToolUse hook to prevent AI agents from skipping git pre-commit hooks with --no-verify and other bypass flags. Use when setting up Claude Code projects that enforce commit quality gates.
what-did-i-get-done
Summarize authored commits over a user-specified time period into a concise update.