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 openEHR/ai-plugins --skill tracker-writinggit clone --depth 1 https://github.com/openEHR/ai-pluginsWrote 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/openehr/ai-plugins/tracker-writing)<a href="https://agentmods.dev/skills/openehr/ai-plugins/tracker-writing"><img src="https://agentmods.dev/badge/skills/openehr/ai-plugins/tracker-writing/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/openehr/ai-plugins/tracker-writing"><img src="https://agentmods.dev/badge/skills/openehr/ai-plugins/tracker-writing.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.00104 | $0.01390 |
| Opus 5.5 | $0.00042 | $0.00556 |
| Sonnet 5.5 | $0.00021 | $0.00278 |
| Haiku 4.5 | $0.00010 | $0.00139 |
Grade A, and why
tracker-writing 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 today.
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 — 134 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Tracker Writing: Jira issues, comments and pull requests
Text posted to a tracker is read by busy SEC members on a phone, in a notification, or in a list of fifty issues. Every word they do not need costs attention. This skill makes every Jira issue, Jira comment and GitHub PR short, structured the same way, and precise.
Style
- Clear. One idea per sentence. Say what is wrong, where, and what should change.
- Precise. Name the class, attribute, section or file. Quote the exact wording in question. Never paraphrase a spec statement when the exact words fit.
- Consistent. Same structure every time, same order of parts, same labels. A reader who has seen one of our tickets can scan the next one.
- Not wordy. No preamble, no restating what the reader already sees (the title, the diff, the parent ticket), no "please note", no closing thanks, no explanation of how the text was produced. Facts and asks only.
Hard caps
| Text | Cap | Counted on |
|---|---|---|
| Jira issue body | 120 words | description field, all parts together |
| Pull request body | 80 words | PR description |
| Jira comment / PR review comment | 40 words | comment body |
| Jira summary / PR title | 80 characters | one line, no trailing period |
Counting: every whitespace-separated token is a word; a URL or an issue key counts as one. Code spans count. Headings and list markers do not.
The caps are hard. The agent does not post text that exceeds them. When the content cannot fit without dropping something the reader needs, follow Over the cap below.
Over the cap
Some texts legitimately need more: a design proposal with options and a fallback, a reproduction with several steps, a review that lists many defects. The rule is:
- Draft the text in the short form first. Remove context, repetition and hedging before removing facts.
- If it still does not fit, do not post. Show the user the draft with its word count and ask one question: post the long form as is, or drop named parts to fit the cap.
- Post what the user chooses. Never cut silently, and never post a long form without that confirmation.
What ships with it
1 file 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.
- today First seen · 134 lines · 104 tokens per session scan A b0d960c9f8be
tracker-writing is a skill published in the GitHub repository openEHR/ai-plugins (3 stars, last pushed yesterday), licensed Apache-2.0. It adds 104 tokens to every session and 1,390 once invoked, about $0.0004 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-17.
Other skills, from other repositories
chief-operating-officer
Owns execution: how work actually gets done across the organization, including process, program management, capacity, vendors, supply chain, and service delivery. Use this when execution is the problem rather than strategy, to design or fix a process, to resolve cross-functional handoff failures, to plan capacity, to…
chief-product-officer
Owns what gets built and why: product strategy, roadmap, discovery, user experience, and the definition of success for each release. Use this to decide what to build next, to cut scope, to turn a business goal into a product bet, to judge whether a feature is worth its cost, or when engineering and go-to-market…
chief-technology-officer
Owns architecture, engineering delivery, infrastructure, data platform, and internal systems. Use this for build-versus-buy calls, technology selection, architectural direction, engineering capacity and delivery risk, technical debt tradeoffs, platform and tooling decisions, or when a technical choice has business…
customer-success-management
Runs the ongoing relationship with accounts after the sale — segmenting coverage against account value, building a health score that predicts rather than describes, running reviews customers find worth attending, forecasting renewals honestly, and finding expansion that follows usage instead of quota. Use this to…
chief-information-officer
The CIO's remit — running the technology the company works on, service quality, IT spend, and the boundary with product engineering. Use this to set IT priorities, decide what IT owns versus engineering, structure IT spend or an IT roadmap, judge whether to build, buy or outsource, or work out why IT is seen as a cost…
service-desk
Runs the IT service desk — intake, triage, prioritization, escalation, knowledge, and the metrics that improve service rather than distort it. Use this to set up or fix a service desk, design ticket priority and escalation, reduce repeat contacts, structure a knowledge base, or work out why a desk hitting its targets…