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 AlpacaLabsLLC/skills-for-architects --skill timetrackergit clone --depth 1 https://github.com/AlpacaLabsLLC/skills-for-architectsWrote 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/alpacalabsllc/skills-for-architects/timetracker)<a href="https://agentmods.dev/skills/alpacalabsllc/skills-for-architects/timetracker"><img src="https://agentmods.dev/badge/skills/alpacalabsllc/skills-for-architects/timetracker/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/alpacalabsllc/skills-for-architects/timetracker"><img src="https://agentmods.dev/badge/skills/alpacalabsllc/skills-for-architects/timetracker.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Agent Snooping · line 148 Skill enumerates or reads other installed skills. Access to other skills' SKILL.md files or the skills directory reveals prompt instructions, capabilities, and secrets that should be invisible to peer skills.Fix: Remove all code or instructions that list or read other skills' files or directories. Skills should operate independently; cross-skill access is a privilege escalation.
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.00081 | $0.02226 |
| Opus 5 | $0.00041 | $0.01113 |
| Sonnet 5 | $0.00016 | $0.00445 |
| Haiku 4.5 | $0.00008 | $0.00223 |
Grade A, and why
timetracker 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 10d 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 — 163 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/as:timetracker — Evidence-Based Manual Time Tracking
Harness note: use
/as:<skill>on Claude Code and$<skill>on Codex. Resolve<skill-root>as the directory containing this loadedSKILL.mdand<plugin-root>as the plugin root that containsskills/, and use equivalent native tools when host tool names differ.
Reconstruct defensible work descriptions from project evidence, ask the user for every duration, preview the proposed rows, and append confirmed entries to one project-level TIMELOG.md.
Usage
/as:timetracker today
/as:timetracker yesterday
/as:timetracker this week
/as:timetracker 2026-07-13 through 2026-07-17
/as:timetracker correct E0012: this was 1.5 hours, not 2.0
Hard rules
- Evidence suggests descriptions, never duration. Never infer hours, start or stop times, billing status, billable category, or completeness from artifact counts, commit counts, timestamp spans, modification times, task status, or meeting duration.
- Every duration comes from the user. Candidate rows always show a blank Hours field. Require a positive user-supplied decimal duration for every selected row before preview or append.
- Preview before mutation. Show the exact rows, including IDs, dates, decimal hours, descriptions, sources, and any correction reference. Append only after explicit confirmation.
- Append only. Never edit, delete, reorder, renumber, or reuse an existing entry. Corrections are new rows that reference the original entry.
- Keep permanent identity. IDs use
E0001,E0002, and so on. Allocate the next ID as the highest parseable existing E-number plus one, including corrective entries. - Cite the trail. Store project-relative Markdown source links. Preserve all distinct relevant sources when several artifacts support one description.
- Do not equate activity with a complete timesheet. Report the paths and evidence channels inspected. A quiet or unreadable source means unknown, not no work.
- Preserve malformed logs. If
TIMELOG.mdcannot be parsed reliably, report the problem and stop before mutation. Do not silently replace or repair it.
What ships with it
2 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.
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.
- 10d ago First seen · 163 lines · 81 tokens per session scan A 4ccf21698b6b
timetracker is a skill published in the GitHub repository AlpacaLabsLLC/skills-for-architects (348 stars, last pushed 7d ago), licensed MIT. It adds 81 tokens to every session and 2,226 once invoked, about $0.0004 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
cre-development
CRE Development and Construction suite - 8 specialist skills for U.S. site/entitlement screening, budget and yield-on-cost, construction loan sizing, GC contracts, draw review, schedule risk, lease-up pro forma, and IC memo writing.
technical-roadmap-planning
Gathers inputs, defines initiatives, prioritises with an impact/effort matrix, sequences dependencies, and produces a roadmap table. Invoked when the user asks to plan a technical roadmap, prioritise engineering initiatives, or create a quarter/half-year engineering plan.
github-issue-planning
Issue-backed plan persistence on GitHub via one managed issue comment with an idempotent marker. Prefers GitHub MCP when available and falls back to gh CLI when MCP is unavailable or misconfigured. Uses local plan persistence only when issue persistence is unavailable or not desired.
module-federation-ssr
Add, review, or debug server-side rendered Module Federation applications, including Modern.js, Nuxt, Next.js legacy Pages Router, Vinext, Vite SSR, and dual browser/server remote artifacts.
codex-symphony
Install and operate a portable OpenAI Symphony + Linear orchestration setup in any Git repository. Use when the user wants a one-command local Symphony runner, a reusable WORKFLOW template, background launch scripts, or a Codex wrapper that restarts Symphony automatically when reopening the CLI.
sparc-pipeline
Use when you need to run the full 5-phase SPARC methodology (Specification→Pseudocode→Architecture→Refinement→Completion) for a complex feature. Each phase has explicit done-criteria gates.