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 BostonOrange/claude-code-framework --skill update-trackergit clone --depth 1 https://github.com/BostonOrange/claude-code-frameworkWrote 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/bostonorange/claude-code-framework/update-tracker)<a href="https://agentmods.dev/skills/bostonorange/claude-code-framework/update-tracker"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/update-tracker/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/bostonorange/claude-code-framework/update-tracker"><img src="https://agentmods.dev/badge/skills/bostonorange/claude-code-framework/update-tracker.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.00037 | $0.00545 |
| Opus 5.5 | $0.00015 | $0.00218 |
| Sonnet 5.5 | $0.00007 | $0.00109 |
| Haiku 4.5 | $0.00004 | $0.00055 |
Grade A, and why
update-tracker 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 1mo 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 — 83 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Update Tracker
Push local story documentation back to the work item tracker.
Usage
/update-tracker TICKET-1234
/update-tracker 1234
Field Mapping
| Tracker Field | Source |
|---|---|
| Description | story.md (User Story, Background, Business Rules, Dependencies) |
| Acceptance Criteria | story.md ## Acceptance Criteria section |
| Test Instructions | how-to-test.md |
| Deployment Notes | story.md ## Technical Specification + manual-steps.md |
Process
Step 1: Parse Input & Locate Docs
Verify local docs exist at docs/stories/TICKET-{id}/:
story.md(required)how-to-test.md(optional)manual-steps.md(optional)
Step 2: Check Ticket Exists
{{TRACKER_FETCH_TICKET}}
If doesn't exist → create it first, then continue. If exists → extract current field values and last modified timestamp.
Step 3: Sync Check
Before overwriting, compare tracker content with local docs:
- Compare last modified timestamps
- If tracker is newer, diff both versions field by field
- Propose merged version incorporating both sides
- Get user approval before pushing
Step 4: Parse story.md into Sections
Split story.md into parts based on section headers:
- Description — everything through Dependencies and Out of Scope
- Acceptance Criteria — the ACs section
- Technical Specification — the tech spec section
Step 5: Build & Push Update
{{TRACKER_UPDATE_FIELDS}}
Step 6: Confirm
After successful update:
- Confirm success with revision info
- Provide direct link to ticket
- Clean up temp files
Edge Cases
| Scenario | Behavior |
|---|---|
story.md missing |
Stop — required |
how-to-test.md missing |
Skip test field update |
manual-steps.md missing |
Deployment notes = tech spec only |
| Tracker updated after local docs | Warn, show diff, offer merge |
| Auth not configured | Prompt user |
Related Skills
/develop— calls this skill in Phase 8/refine-story— story refinement/draft-story— draft new stories
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.
- 1mo ago First seen · 83 lines · 37 tokens per session scan A 75b4a22111d1
update-tracker is a skill published in the GitHub repository BostonOrange/claude-code-framework (3 stars, last pushed 3mo ago), licensed MIT. It adds 37 tokens to every session and 545 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-08-31.
Other skills, from other repositories
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
handle-linkedin-connection-request-signal
Use this skill when someone sends a team member an inbound LinkedIn connection request. An inbound request is a deliberate, ACTIVE first-party intent signal — meaningfully stronger than a passive profile view — and it deserves different scoring rules. The skill resolves and enriches the requester, gates them through…