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 LuisUrrutia/skills --skill report-work-activitygit clone --depth 1 https://github.com/LuisUrrutia/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/luisurrutia/skills/report-work-activity)<a href="https://agentmods.dev/skills/luisurrutia/skills/report-work-activity"><img src="https://agentmods.dev/badge/skills/luisurrutia/skills/report-work-activity/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/luisurrutia/skills/report-work-activity"><img src="https://agentmods.dev/badge/skills/luisurrutia/skills/report-work-activity.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.00020 | $0.01245 |
| Opus 5.5 | $0.00008 | $0.00498 |
| Sonnet 5.5 | $0.00004 | $0.00249 |
| Haiku 4.5 | $0.00002 | $0.00125 |
Grade A, and why
report-work-activity 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 17d 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 — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Report work activity
Produce a concise HTML report with retained evidence and useful counts, separating
work from open source. One collection supports both the historical report and a
separate snapshot of outstanding work. This skill replaces daily-meeting-update.
It reports activity; code reviews, incident response and task execution keep their
own workflows. A request for pending work alone uses the same evidence contract.
Establish the report
Resolve the requested period, IANA timezone, known accounts, work organizations and repositories, and a private local output directory from available context. Ask only for missing facts that materially affect scope or attribution. Do not start with a standup interview. Discover all relevant connected sources, including ones outside the current repository; an available tool is not proof of access or complete history. Record excluded and unavailable sources visibly.
Read references/evidence.md before collection. Resolve calendar periods once with the bundled helper: yesterday, previous week (Monday start unless configured), previous month, or an explicit interval. Retain the inclusive start, exclusive end, timezone and snapshot time. Historical events belong by action time; current assignments can predate the period.
Confirm provider identities and aliases. For GitHub, discover all configured gh
accounts and hosts, including inactive profiles, using
references/engineering-sources.md.
Map repositories, organizations and other containers to work, open-source,
personal or unclassified. Public
employer repositories are work. Unknown classification stays visible; repository
visibility, a display name, or the current checkout cannot settle ownership.
Preserve confirmed mappings locally for later reports, without credentials. Read
references/bundle.md to resolve the private report root,
mapping file and separate worker paths before delegation.
What ships with it
15 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
- assets/report.css 3.5 KB
- origin.toml 21 KB
- references/agent-history.md 2.5 KB
- references/bundle.md 9.9 KB
- references/collaboration-sources.md 4.1 KB
- references/engineering-sources.md 8.0 KB
- references/evidence.md 5.0 KB
- references/extraction.md 3.3 KB
- scripts/activity_report.py 2.0 KB runs code
- scripts/ledger.py 11 KB runs code
- scripts/period.py 1.9 KB runs code
- scripts/render_report.py 9.7 KB runs code
- tests/fixtures.py 9.3 KB runs code
- tests/test_activity_report.py 14 KB runs code
- THIRD-PARTY-NOTICES.txt 8.1 KB
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.
- 17d ago Changed · -3 lines 290fa1dc4791
- 1mo ago First seen · 115 lines · 20 tokens per session scan A f428fd3c2149
report-work-activity is a skill published in the GitHub repository LuisUrrutia/skills (2 stars, last pushed today), licensed MIT. It adds 20 tokens to every session and 1,245 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-10-06.
Other skills, from other repositories
capabilities-manager
Manage capa CLI configuration — capabilities.yaml / capabilities.json, skills, MCP servers, tools, hooks, sub-agents, rules, plugins, AGENTS.md / CLAUDE.md, security options, tool exposure modes, capa wrap shadow workspaces, --passthrough native writes, registries (including Claude marketplaces), activity traces, and…
bootstrap
Capify an existing project. Scans the repo for already-installed MCP servers, skills, rules, hooks, sub-agents, and plugins (across .claude, .cursor, .codex, .gemini, etc.), consolidates them into shared top-level directories (skills/, rules/, hooks/), and synthesizes a sound capabilities.yaml from the inventory. Use…
create-roadmap
Generates a battle-tested, phased master roadmap (progress.md) from any app idea or feature spec. Breaks development into foundational infrastructure, modular features, settings, monetization, security, polish, and store publishing, modeled after production systems like Floatkit.
project-scaffold
Scaffolds a complete project memory and multi-agent coordination system (gemini.md, AGENTSYNC.md, progress.md, taskplan.md, findings.md, crash-log.txt, .env.example, .gitignore). Provides a streamlined, stack-agnostic alternative to the B.L.A.S.T. protocol for deterministic development and seamless agent handoffs.
constraint-driven-development
Use when an Android project has no written quality bar, when the user says "set up constraints" or "define our standards", when coverage, performance, or accessibility should become enforced gates instead of per-PR arguments, when an agent keeps silencing checks or skipping tests to get to green, or when a threshold…
android-ui-engineering
Use when building UI with Jetpack Compose. Covers component design, state hoisting, recomposition optimization, Material 3 theming, Navigation 3, adaptive layouts for large screens, previews, screenshot verification, and XML interop.