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 lucasviola/specwiki --skill track-package-locallygit clone --depth 1 https://github.com/lucasviola/specwikiWrote 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/lucasviola/specwiki/track-package-locally)<a href="https://agentmods.dev/skills/lucasviola/specwiki/track-package-locally"><img src="https://agentmods.dev/badge/skills/lucasviola/specwiki/track-package-locally/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/lucasviola/specwiki/track-package-locally"><img src="https://agentmods.dev/badge/skills/lucasviola/specwiki/track-package-locally.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.00036 | $0.00339 |
| Opus 5 | $0.00018 | $0.00169 |
| Sonnet 5 | $0.00007 | $0.00068 |
| Haiku 4.5 | $0.00004 | $0.00034 |
Grade A, and why
track-package-locally 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.
What it actually says
Track package locally
Reproduce tracking behaviour on your machine without touching production credentials.
Quick commands
npm install
npm test # baseline
npm run dev -- track --id DEMO-1001
npm run dev -- track --id DEMO-1001 --verbose
npm run typecheck
Debugging workflow
- Pick a fixture id — start with
DEMO-1001(offline fixture intests/fixtures/). - Run with
--verbose— confirm timeline order and next-action copy; watch for raw status codes leaking to stdout. - Isolate the layer:
- CLI parse error → fix argument parsing first (
exit 1). - Adapter throws → check fixture path and carrier mapping (
exit 2). - Formatting wrong → fix
formatTimeline()/ next-action mapping only.
- CLI parse error → fix argument parsing first (
- Add a failing test — capture the bug as a table-driven case before fixing.
Checklist before you finish
- Output is plain language (“Out for delivery today” not
OFD) - Verbose mode redacts tokens and full addresses
-
npm testpasses for the carrier you touched
Common mistakes
- Calling live carrier APIs during local dev — use fixtures unless explicitly testing integration.
- Logging full tracking URLs — strip query tokens in verbose output.
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 · 42 lines · 36 tokens per session scan A 67caf4086102
track-package-locally is a skill published in the GitHub repository lucasviola/specwiki (11 stars, last pushed 1mo ago), licensed MIT. It adds 36 tokens to every session and 339 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
debug-optimize-lcp
Guides debugging and optimizing Largest Contentful Paint (LCP) using Chrome DevTools MCP tools. Use this skill whenever the user asks about LCP performance, slow page loads, Core Web Vitals optimization, or wants to understand why their page's main content takes too long to appear. Also use when the user mentions…
systematic-debugging
Use when debugging a failing test, build error, or runtime issue that isn't immediately obvious. Guides a 4-phase root cause analysis instead of random fix attempts.
diagnose
Trace from a reproduced symptom to the source code that causes it. Pin the specific file and approximate line, rate confidence in the cause and clarity of the fix independently, and always propose a concrete fix.
repro-admin
Reproduce an EmDash admin UI bug. Attach a container, start the demo dev server, drive the admin with agent-browser using the dev-bypass session, and capture the reproduction as screenshots plus a replayable transcript.
log-error-digest
Analyze log files to troubleshoot errors, identify peak error periods, and produce error clustering, frequency statistics, and time distribution reports. Supports JSON, syslog, and Nginx formats with automatic detection. Use when a user uploads a .log file and asks to analyze errors, find patterns, debug issues, or…
byted-util-volcengine-detect-retry
An orchestration workflow for Volcengine Cloud Detect, a service that checks websites or network endpoints from test locations.