Borrowing it
Nothing to install: this file belongs to HenriqueCotta/ownership-driven-ai-customization-architecture. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/HenriqueCotta/ownership-driven-ai-customization-architecture/main/.github/skills/oda-task-tracking/SKILL.mdgit clone --depth 1 https://github.com/HenriqueCotta/ownership-driven-ai-customization-architectureWrote 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/henriquecotta/ownership-driven-ai-customization-architecture/oda-task-tracking)<a href="https://agentmods.dev/skills/henriquecotta/ownership-driven-ai-customization-architecture/oda-task-tracking"><img src="https://agentmods.dev/badge/skills/henriquecotta/ownership-driven-ai-customization-architecture/oda-task-tracking/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/henriquecotta/ownership-driven-ai-customization-architecture/oda-task-tracking"><img src="https://agentmods.dev/badge/skills/henriquecotta/ownership-driven-ai-customization-architecture/oda-task-tracking.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.00041 | $0.00495 |
| Opus 5 | $0.00020 | $0.00247 |
| Sonnet 5 | $0.00008 | $0.00099 |
| Haiku 4.5 | $0.00004 | $0.00049 |
Grade A, and why
oda-task-tracking 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 11d 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 — 61 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ODA Task Tracking
Use this skill for operational work with repository issues and the ODA Board.
This is a workflow for task tracking, not a path-specific coding rule.
Scope
Repository: HenriqueCotta/ownership-driven-ai-customization-architecture
Project: ODA Board
Project owner: HenriqueCotta
Project number: 4
Task Contract
A tracked task is a repository issue that may also be represented by the same issue as a project item.
The project Status field is the board status. Use only Todo, In Progress, or Done.
Use existing repository labels when they fit. Do not invent a label taxonomy or create new labels unless the user explicitly asks.
There is no board Area field. Do not simulate one in issue text unless the user asks for a planning convention change.
Interpret board authority according to ownership/repository/oda-board.instructions.md.
Workflow
Search for existing issues before creating a new tracked task.
When creating or rewriting an issue, keep the body concise and actionable with outcome, context, acceptance criteria, and verification.
After a create or update operation, keep the issue body, labels, project status, and linked updates coherent.
When moving a task, update the project status to the requested valid value or the closest valid value. Ask one focused question only when ambiguity would change the result.
When listing work or answering what is next, prefer open Todo items and explain the priority briefly from board state and repository context.
Access Failure
If GitHub issue access is unavailable, do not create or update task state.
If project access is unavailable but issue access works, update only the issue when that still satisfies the request and clearly report that board synchronization is blocked.
If the board state could change the answer, treat that part as verification-blocked instead of guessing.
Guardrails
Never delete issues or project items.
Do not close or mark work Done unless the user asks for that change or the repository evidence clearly supports it.
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.
- 11d ago First seen · 61 lines · 41 tokens per session scan A cef4f0973f6f
oda-task-tracking is a skill published in the GitHub repository HenriqueCotta/ownership-driven-ai-customization-architecture (5 stars, last pushed 4mo ago), licensed MIT. It adds 41 tokens to every session and 495 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
commit
Stage, commit, and push code changes with branch safety and explicit staging. Use when ready to commit work. Invoked by saying "commit", "push", or "commit and push".
document-task
Document completed work — update task log, sync documentation, log observations. Use after finishing a task or batch of changes.
commit-all
Batch-commit all uncommitted changes grouped by relevance. Use when multiple accumulated changes need committing. Invoked by saying "commit all" or "commit everything".
merge-master
Merge dev branch into master/main and push. Use when dev changes are ready for production branch. Invoked by saying "merge to master" or "merge to main".
close-task-commit-push-pr
Close the active backlog task (detected from branch name), commit all changes, push to remote, and open a pull request. Use when the user says "close task and ship it", "close task commit push pr", or invokes /close-task-commit-push-pr.
start-task
Create a feature branch for a backlog task, switch to it, and start implementation. Use when the user says "start task-123", "work on task-123", "implement task-123", or invokes /start-task with a task ID.