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 agentmods add skills/beeltec/context-usage-mcp/to-tasksnpx skills add beeltec/context-usage-mcp --skill to-tasksgit clone --depth 1 https://github.com/beeltec/context-usage-mcpWrote 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/beeltec/context-usage-mcp/to-tasks)<a href="https://agentmods.dev/skills/beeltec/context-usage-mcp/to-tasks"><img src="https://agentmods.dev/badge/skills/beeltec/context-usage-mcp/to-tasks.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 | $0.00043 | $0.00201 |
| Opus 5 | $0.00022 | $0.00101 |
| Sonnet 5 | $0.00009 | $0.00040 |
| Haiku 4.5 | $0.00004 | $0.00020 |
Grade A, and why
to-tasks 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.
What it actually says
If the folder docs/tasks does not exist yet, create it and add it to the .gitignore file
Break the work down into smaller tasks that will likely not exceed a context window of 175.000 tokens. Create task documents out of it in docs/tasks/{shell_safe_branch_name}/{001}_description.md.
Each task document should have comprehensive instructions and a markdown checklist of all substasks this task contains.
Create one master task document that contains a summary of all of the work that needs to be done and add links to all tasks including their status.
Each task document should also have a link to the master document, the previous task document and the next task document.
Make sure to refrence the necessary internal OKF wiki entries in the task documents
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.
- 3d ago First seen · 17 lines · 43 tokens per session scan A e2d8ead1edf0
to-tasks is a skill published in the GitHub repository beeltec/context-usage-mcp (0 stars, last pushed 1mo ago), licensed MIT. It adds 43 tokens to every session and 201 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-31.
Other skills, from other repositories
report-issue-framework
File a bug or feature request against @cyanheads/mcp-ts-core when you hit a framework issue. Use when a builder, utility, context method, or config behaves contrary to the documented API — not for server-specific application bugs.
report-issue
File a bug or feature request against this repository (cyanheads/git-mcp-server) using the gh CLI. Use for tool logic bugs, git provider misbehavior, transport issues, auth/config problems, or new feature proposals.
approval-workflows
Configure ServiceNow approval rules and sysapprovalapprover records — manager/group/script approvers, multi-level routing, delegation via sysuserdelegate, and parent-record state rollup.
change-management
Create and transition ServiceNow change requests (normal/standard/emergency), change tasks, affected CIs, approval routing, CAB scheduling, and conflict detection across maintenance windows.
hr-service-delivery
Build ServiceNow HR Service Delivery — snhrcorecase from Employee Center or HR catalog, snhrlelifecycleevent onboarding/offboarding with templated activities, and HR document generation.
incident-management
Manage ServiceNow incidents — creation with impact/urgency priority calc, auto-assignment by category, reassignment tracking, major incident declaration with bridge calls, time-based escalation, MTTR metrics.