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 daddia/claude-for-strategy --skill tracker-buildergit clone --depth 1 https://github.com/daddia/claude-for-strategyWrote 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/daddia/claude-for-strategy/tracker-builder)<a href="https://agentmods.dev/skills/daddia/claude-for-strategy/tracker-builder"><img src="https://agentmods.dev/badge/skills/daddia/claude-for-strategy/tracker-builder.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.00060 | $0.01058 |
| Opus 5 | $0.00030 | $0.00529 |
| Sonnet 5 | $0.00012 | $0.00212 |
| Haiku 4.5 | $0.00006 | $0.00106 |
Grade A, and why
tracker-builder 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.
How it starts
The opening of the file, as written. The whole thing — 102 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tracker Builder
When to use
Build actual .xlsx tracker — Daily Log tab feeding Summary via live formulas — replicating practice profile pattern, not generic template.
What this skill does not do
- Does not define metrics — route to
/performance:metrics-glossaryor/performance:kpi-tree-builderfirst. - Does not invent raw input columns — ask for actual source fields.
- Does not redesign existing tracker — extends/replicates profile pattern.
Preconditions
| Input | If missing |
|---|---|
| Performance practice profile (tracker structure) | Ask; default Daily Log + SUMIFS summary with [PROVISIONAL] |
| Metric list for this tracker | Ask which metrics and category codes |
| xlsx build guidance | Read /mnt/skills/public/xlsx/SKILL.md before building |
Provisional mode
No existing pattern in profile: default Daily Log + Summary with AVERAGEIFS/SUMIFS movement columns; document formula logic tab.
Trust spine
- Confidence bands (
structured-aggregation):- High: Live formulas wired; raw inputs separate from calculated; formula doc included.
- Medium: Some raw inputs
INPUT NEEDEDflagged in notes. - Low: Metric list undefined — halt build.
- Failure modes:
- Strategic advice vs. support: Tracker is draft structure for owner validation.
- Client confidentiality: Tracker may contain proprietary metrics — CONFIDENTIAL header on docs.
- Accountability gap: Formula logic documented for maintainability.
- Analytical Rigor: Completeness — every summary metric traces to log inputs.
- Incentive Gaming: N/A — build focus.
- Escalation triggers: Raw input unspecified — flag, don't invent column.
Workflow
- Read practice profile for existing tracker structure.
- Confirm metric list and category codes.
- Design Daily Log — one row per period, columns for raw inputs only.
- Design Summary — movement columns via AVERAGEIFS/SUMIFS per profile pattern.
- Build
.xlsxwith live formulas per xlsx skill guidance. - Document formula logic in notes tab or section.
- Flag unspecified raw inputs — don't invent.
- Connector seed data. When seeding from
~~bi analyticsor~~spreadsheetMCP pulls, tag imported figures[sourced: <connector>, <workbook/dataset>, <as-of>]in the tracker notes tab; never paste uncited connector numbers into Summary formulas. - Completeness check before delivery.
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 · 102 lines · 60 tokens per session scan A 82de13253616
tracker-builder is a skill published in the GitHub repository daddia/claude-for-strategy (2 stars, last pushed 2mo ago), licensed MIT. It adds 60 tokens to every session and 1,058 once invoked, about $0.0003 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-09-03.
Other skills, from other repositories
build-parameterized-report
Create parameterized Quarto or R Markdown reports that can be rendered with different inputs to generate multiple variations. Covers parameter definitions, programmatic rendering, and batch generation. Use when generating the same report for different departments, regions, or time periods; creating client-specific…
markitdown
Convert files, URLs, and documents to Markdown using the markitdown MCP server. Activate when the user asks to convert, extract, or read content from PDFs, Word docs, PowerPoints, spreadsheets, images, audio files, or any URL.
pn-financial-model-audit
Audit a financial model (spreadsheet, structured table, or agent-produced model) for hardcoded values, broken formula logic, balance-sheet balance, circular references, and missing cross-checks. Use after any DCF, LBO, comps, or 3-statement model is built before it is used in a deliverable.
figma-a11y-audit
Generates a formatted Excel accessibility audit report from Figma file comments with visual evidence screenshots. Parses structured audit comments containing WCAG criteria, error descriptions, and proposed solutions. Captures PNG evidence of each affected component and outputs a professional errores-accesibilidad.xlsx…
xlsx
Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or…
xlsx
Comprehensive spreadsheet creation, editing, and analysis with support for formulas, formatting, data analysis, and visualization. When Claude needs to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv, etc) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing data, (3) Modify…