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 agentmods add skills/aeonfun/aeon/shiplognpx skills add aeonfun/aeon --skill shiploggit clone --depth 1 https://github.com/aeonfun/aeonWrote 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/aeonfun/aeon/shiplog)<a href="https://agentmods.dev/skills/aeonfun/aeon/shiplog"><img src="https://agentmods.dev/badge/skills/aeonfun/aeon/shiplog.svg" alt="Measured on agentmods" 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.00046 | $0.05156 |
| Opus 5 | $0.00023 | $0.02578 |
| Sonnet 5 | $0.00009 | $0.01031 |
| Haiku 4.5 | $0.00005 | $0.00516 |
Grade A, and why
shiplog scanned grade A with 1 finding 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 yesterday.
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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
### 3. X activity (direct X.AI curl — primary) Copies of this mod
1 near-identical copy found in the catalogue:
- shiplog — 100% identical, 0 lines differ
How it starts
The opening of the file, as written. The whole thing — 245 lines — stays where its author put it; the contents beside it link to each section on GitHub.
${var} — Optional, space-separated flags:
since:YYYY-MM-DD— override the window start (default: when this skill last ran).days:N— window = last N days.dry-run— render to stdout; write no article, no state, no notify.owner/repo— narrow GitHub coverage to that one repo.- any other word — focus/theme filter (a product name or keyword).
Empty = everything shipped since the last run, across all configured repos.
Produce two artifacts:
- Digest — a themed, human-readable recap of everything that shipped + traction (the article).
- Shiplog post — a tight, bulleted, ready-to-post version in the operator's voice, every project @-tagged (the notification).
This is cadence-agnostic: the window is always "since the last run" (memory/state/shiplog-last.json), so the aeon.yml schedule alone decides whether this is a daily, weekly, or on-demand recap. One skill, any frequency.
Read STRATEGY.md, memory/MEMORY.md, and the last 7 days of memory/logs/ for context. Read soul/SOUL.md + soul/STYLE.md before writing any output — the shiplog post must sound like the operator, not a changelog bot. If soul/ is empty, use a clear, direct, neutral voice (drop the signature flourishes below).
Config — all derived, nothing hardcoded
operator = gh api user --jq .login # the authenticated operator (PR-author search)
product_handles = memory/products.md `handles:` lines (@x) # product X accounts to read
flagship_repos = memory/products.md `repos:` tagged (public) # the star / north-star story
watched_repos = memory/watched-repos.md, else products.md repos: # everything shipped across
ecosystem_scouts= memory/products.md `scouts:` line (optional) # recap accounts to scan for features
star_state = memory/state/shiplog-stars.json # snapshot for week-over-week star deltas
If neither watched-repos.md nor products.md yields a repo, exit SHIPLOG_NO_REPOS (notify + log, no article). Sections whose config is absent (X handles, scouts) are skipped gracefully, not failed.
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.
- yesterday First seen · 245 lines · 46 tokens per session scan A 6dd3aa21b17b
shiplog is a skill published in the GitHub repository aeonfun/aeon (716 stars, last pushed today), licensed MIT. It adds 46 tokens to every session and 5,156 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-05.
Other skills, from other repositories
batch
Research and plan a large-scale change, then execute it in parallel across 5–30 isolated worktree agents that each open a PR.
agent-framework-py-release
Use when cutting a Python release for the microsoft/agent-framework monorepo. Triggers on "bump py versions", "cut a python release", "prepare release PR for python", "release py packages", "bump python to X.Y.Z", or similar requests to bump Python package versions and prepare a release PR. Handles all four lifecycle…
github
Drive GitHub via the official gh CLI — repos, issues, pull requests, releases, gists, Actions runs, and raw REST through gh api. Use when the user asks to inspect or manage GitHub.
create-milestone
Create a GitHub milestone for an upcoming release. Suggests the next version based on the latest release, gathers all merged PRs and closed issues since that release, presents a draft with two tables (Issues and PRs) for user approval, then creates the milestone and assigns all approved items.
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
no-mistakes
Validate committed feature-branch changes through the no-mistakes pipeline: intent, rebase, review, test, docs, lint, push, PR, and CI. Use when the user asks to run no-mistakes, ship safely, validate before pushing, or gate a change before it reaches upstream.