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/jmagly/aiwg/activity-lognpx skills add jmagly/aiwg --skill activity-loggit clone --depth 1 https://github.com/jmagly/aiwgWrote 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/jmagly/aiwg/activity-log)<a href="https://agentmods.dev/skills/jmagly/aiwg/activity-log"><img src="https://agentmods.dev/badge/skills/jmagly/aiwg/activity-log.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.00021 | $0.01452 |
| Opus 5 | $0.00010 | $0.00726 |
| Sonnet 5 | $0.00004 | $0.00290 |
| Haiku 4.5 | $0.00002 | $0.00145 |
Grade A, and why
activity-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 6d 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 — 186 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Activity Log
You query and manage the unified .aiwg/activity.log — a chronological record of all framework operations across SDLC, research, and other AIWG-managed workflows.
Triggers
Alternate expressions and non-obvious activations (primary phrases are matched automatically from the skill description):
- "what happened recently" → show (default limit)
- "show me today's activity" → show --since today's date
- "log a create operation" → append create
- "how many deploys have we done" → stats
- "activity since last week" → show --since YYYY-MM-DD
Trigger Patterns Reference
| Pattern | Example | Action |
|---|---|---|
| Recent activity | "show activity log" | activity-log show |
| Filtered by date | "activity since 2026-04-10" | activity-log show --since 2026-04-10 |
| Filtered by operation | "show all deploys" | activity-log show --operation deploy |
| Limited output | "last 5 entries" | activity-log show --limit 5 |
| Manual append | "log that we archived the SAD draft" | activity-log append archive <summary> |
| Statistics | "how many operations by type" | activity-log stats |
Behavior
When triggered:
-
Identify the subcommand:
show— display entries, optionally filteredappend— add a manual entrystats— summarize operation counts and date range
-
Locate the log file:
.aiwg/activity.logrelative to the project root. If the file does not exist, report it as empty (do not error). -
Execute the subcommand:
show
Display entries in reverse-chronological order (newest first).
# Show last 20 entries (default)
aiwg activity-log show
# Filter by date (inclusive)
aiwg activity-log show --since 2026-04-10
# Filter by operation type
aiwg activity-log show --operation deploy
# Limit output count
aiwg activity-log show --limit 5
# Combine filters
aiwg activity-log show --since 2026-04-10 --operation create --limit 10
Accepted --operation values: ingest, create, update, delete, query, lint, deploy, archive, promote
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.
- 6d ago First seen · 186 lines · 21 tokens per session scan A 8bed52e1d371
activity-log is a skill published in the GitHub repository jmagly/aiwg (209 stars, last pushed today), licensed MIT. It adds 21 tokens to every session and 1,452 once invoked, about $0.0001 per session on Opus 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
goal-writer
Drafts a goal+rider document pair that briefs an autonomous coding agent on one round of work — a goal file under 4,000 characters (sized to fit the /goal command in both Claude Code and Codex) plus an unbounded rider with phased plans and named depth tests. Use when the user says "draft a goal", "write a goal+rider"…
surge
Use when a user provides a PRD, spec, or detailed requirements document and needs a full project delivered through iterative expert orchestration — multi-round analyze/research/design/implement/QA cycles with convergence detection. NOT for: single-file edits, quick prototypes, simple Q&A, or tasks without a written…
horizon
Run a durable Horizon workflow for a multi-feature goal with bounded autonomous retries and an audit trail.
check-in
Record a Parallax protocol checkpoint with concrete evidence before gated implementation work.
debug
Perform an evidence-based Parallax diagnosis or post-build audit and verify the repair.
hyperplan
Harden a non-trivial plan through a three-round adversarial critique and evidence-based synthesis.