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/syi0808/screenize/work-loggernpx skills add syi0808/screenize --skill work-loggergit clone --depth 1 https://github.com/syi0808/screenizeWrote 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/syi0808/screenize/work-logger)<a href="https://agentmods.dev/skills/syi0808/screenize/work-logger"><img src="https://agentmods.dev/badge/skills/syi0808/screenize/work-logger.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 | $0.00047 | $0.00529 |
| Opus 5 | $0.00023 | $0.00264 |
| Sonnet 5 | $0.00009 | $0.00106 |
| Haiku 4.5 | $0.00005 | $0.00053 |
Grade A, and why
work-logger 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 3d 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.
What it actually says
WORK LOGGING PROTOCOL
Index completed work for future context retrieval via semantic search.
When to use: Execute /log-work after every meaningful work unit (features, bugs, refactors, config changes).
Step 1: Generate Template
uv run .claude/skills/work-logger/scripts/create_template.py \
--description "short-description" \
--type feature|bugfix|refactor|docs|config
Output: private-docs/work-logs/YYYY-MM-DD-short-description.md
Step 2: Populate Log
Edit the generated file:
- Metadata: Fill
tags(YAML array) andfiles_changed - Content: Complete
summary, Title, and all sections - Quality: Ensure self-contained, searchable text
Step 3: Index to Vector DB
uv run .claude/skills/sqlite-vectordb/scripts/add_entry.py \
--file "private-docs/work-logs/YYYY-MM-DD-short-description.md" \
--summary "One-line summary" \
--tags "tag1,tag2"
- Language: All indexed data (summary, tags) MUST be in English for vector DB compatibility
- Integrity: Logs must be understandable in isolation with verified filenames/paths
- Context: Use project conventions from
CLAUDE.md - Completeness: Include decisions made and rationale
Valid usage:
# Step 1: Generate
uv run .claude/skills/work-logger/scripts/create_template.py \
--description "add-user-auth" --type feature
# Step 2: Edit private-docs/work-logs/2026-01-16-add-user-auth.md
# Step 3: Index
uv run .claude/skills/sqlite-vectordb/scripts/add_entry.py \
--file "private-docs/work-logs/2026-01-16-add-user-auth.md" \
--summary "Implemented OAuth2 user authentication" \
--tags "auth,oauth,security"
What ships with it
1 file 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.
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.
- 3d ago First seen · 76 lines · 47 tokens per session scan A 5787a916b11f
work-logger is a skill published in the GitHub repository syi0808/screenize (601 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 47 tokens to every session and 529 once invoked, about $0.0002 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
html-ppt-hermes-cyber-terminal
OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.
test-conversion
Workflow for converting unit tests to browser tests for Project Bedrock. Invoke this when the user wants to remove complex Browser dependencies from tests.
feishu
Work with Feishu or Lark bots, docs, sheets, bitables, approval flows, and OpenAPI/MCP setup without hardcoding credentials.
review-agentic-workflows
Review agentic workflow changes for correctness, security posture, and optimization opportunities with compile, validation, and audit evidence.
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
diagnostic-stem-delivery
Audio production with diagnostic analysis, timecode parsing from documents, and verified export workflow.