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 jamditis/claude-skills-journalism --skill goal-progress-bargit clone --depth 1 https://github.com/jamditis/claude-skills-journalismWrote 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/jamditis/claude-skills-journalism/goal-progress-bar)<a href="https://agentmods.dev/skills/jamditis/claude-skills-journalism/goal-progress-bar"><img src="https://agentmods.dev/badge/skills/jamditis/claude-skills-journalism/goal-progress-bar/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/jamditis/claude-skills-journalism/goal-progress-bar"><img src="https://agentmods.dev/badge/skills/jamditis/claude-skills-journalism/goal-progress-bar.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.00021 | $0.00688 |
| Opus 5.5 | $0.00008 | $0.00275 |
| Sonnet 5.5 | $0.00004 | $0.00138 |
| Haiku 4.5 | $0.00002 | $0.00069 |
Grade A, and why
goal-progress-bar 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 yesterday.
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 — 78 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Goal progress bar
Use this skill for work with three or more steps that runs long enough for someone to ask how close it is to done. Skip it for a quick answer or one-step task.
Each task gets one tracker file. The script renders the current percentage, bar, and row status at each checkpoint. Never type or adjust those values by hand.
Set up a tracker
- Write
<goal>-progress.jsonin your task folder. The file is a JSON list of[name, weight, fraction]rows. - Use one row for each deliverable or proof that moves the goal. Examples include code, review, release, live verification, and requester approval. Use names the requester understands.
- Use weight
1for a small row and2for a large or critical row. End with the rows that prove the work is complete in real use. - Add a fourth field to a row that cannot move:
[name, weight, fraction, "blocked"]. Remove the field when work resumes.
Render the tracker
Run the script from the task folder. Replace <skill-root> with the folder
that contains this SKILL.md:
python3 <skill-root>/scripts/progress.py <goal>-progress.json "<Goal name>"
Add --chat for emoji codes suited to chat systems that render common emoji
shortcodes:
python3 <skill-root>/scripts/progress.py <goal>-progress.json "<Goal name>" --chat
The chat bar uses green squares for complete work, one yellow square for partial work, and white squares for the rest. Each row starts with a green, yellow, white, or red status circle. Send the rendered text without a code block if the destination converts emoji codes.
Update at each checkpoint
A checkpoint is a finished step, such as a reviewed change, release, live check, or answer from the requester.
- Back up the tracker before each edit, for example:
cp <goal>-progress.json <goal>-progress.json.bak-<date>-<time>. - Set a code row to
1.0only when its defined work is complete. - Set a proof row to
1.0only with real evidence, such as a receipt, live read, or requester answer. Never round up to done before the proof exists. - Add a row when the goal grows. Never delete a row to raise the percentage.
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.
- yesterday First seen · 78 lines · 21 tokens per session scan A 5b3db8fd41a5
goal-progress-bar is a skill published in the GitHub repository jamditis/claude-skills-journalism (433 stars, last pushed 2d ago), licensed MIT. It adds 21 tokens to every session and 688 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-10-25.
Other skills, from other repositories
customer-onboarding-and-implementation
Takes a new customer from signature to working — setting a definition of live that both sides agreed before the contract was signed, planning and staffing the implementation, running data migration and integration realistically, training the people who will actually use it, and handing over to the ongoing…
estimating-and-contingency
Produces a cost or effort estimate someone can defend — decomposing the work, choosing between analogous, parametric and bottom-up methods, documenting the basis and its assumptions, expressing confidence as a range, and sizing contingency and management reserve separately. Use this to build an estimate, challenge one…
scenario-team-admin
Use when administering a Scenario team from an agent through MCP: restricting which models a team or project can run (model access control, allowlist, blocklist), inviting or removing team and project members, changing roles, capping a member's Creative Unit spend, creating or deleting projects, auditing API keys and…
aejpol-submission
Use when running the final pre-submission preflight for AEJ: Economic Policy via the AEA online submission system — single-blind review front matter, JEL codes, submission and publication fees, format, the Data and Code Availability Statement, and disclosure. Final checks; it does not draft content.
amann-submission
Use when running the final pre-submission preflight for an Academy of Management Annals (Annals) proposal or invited full review via the Manuscript Central portal — proposal-vs-invited-review route, deadlines, formatting, CV, and anonymity. Final checks; it does not draft content.
data-evolution-analysis
Analyze data evolution patterns in construction organizations. Assess digital maturity and data strategy for construction companies.