Borrowing it
Nothing to install: this file belongs to sean-galloway/RTLDesignSherpa. 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/sean-galloway/RTLDesignSherpa/main/.claude/skills/tasks/SKILL.mdgit clone --depth 1 https://github.com/sean-galloway/RTLDesignSherpaWrote 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/sean-galloway/rtldesignsherpa/tasks)<a href="https://agentmods.dev/skills/sean-galloway/rtldesignsherpa/tasks"><img src="https://agentmods.dev/badge/skills/sean-galloway/rtldesignsherpa/tasks/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/sean-galloway/rtldesignsherpa/tasks"><img src="https://agentmods.dev/badge/skills/sean-galloway/rtldesignsherpa/tasks.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00067 | $0.00686 |
| Opus 5 | $0.00034 | $0.00343 |
| Sonnet 5 | $0.00013 | $0.00137 |
| Haiku 4.5 | $0.00007 | $0.00069 |
Grade A, and why
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 9d 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 — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
tasks
READ FIRST: /vault/Tasks/INDEX.md (the master index IS the authority for this convention).
All task tracking lives in /vault/Tasks/<area>/. Each area has INDEX.md plus four
lifecycle pages: open.md (ready to start), active.md (in progress),
deferred.md (deliberately parked - the block must NAME the condition that
un-defers it; created per-area on first need), closed.md (done),
dropped.md (ended without completing).
The rule agents break: never create a TASKS.md / TODO.md / *_TODO.md
next to code. That scatter is what /vault/Tasks/ replaces. A note-to-self goes in
/vault/Tasks/<area>/open.md, not in a new file beside the module.
Move a task by CUTTING its block between pages (never copy - one state only),
and keep its **Status:** line dated. closed = done; dropped = decided not
to do it - keep them apart so history stays honest.
Migration is in progress (tracked as TOOL-001 in vault/Tasks/tooling/active.md):
amba is migrated; other areas' rows in /vault/Tasks/INDEX.md are marked pending
and still point at their old file until moved.
Migrating an area (do every area identically)
- Fence-aware split the source file into task blocks. Only treat a line
starting with
##/###as a header when NOT inside a ``` code fence — task bodies embed markdown/code examples whose lines start with##, and a naive split silently drops the tail of those tasks. - Classify by REAL repo state, not the stale
**Status:**marker. Verify each task against the tree (does the file/feature exist, did the work land?). The amba pilot's "active" bucket was mostly already done. closed = done, dropped = decided-against. - Write
INDEX.md+open/active/closed/dropped.md(see vault/Tasks/amba/ for the shape). Keep each task block intact; drop only scaffolding (legends, phase headers, stale summary tables). - Repoint every inbound reference to /vault/Tasks// and delete the original file (owner's chosen policy).
- Verify: task-block count and content match the original; all links resolve. The counts looking clean is not proof — the first amba pass looked clean and had dropped a task's tail.
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.
- 9d ago First seen · 49 lines · 67 tokens per session scan A 8d56c9ee551b
tasks is a skill published in the GitHub repository sean-galloway/RTLDesignSherpa (23 stars, last pushed today), licensed MIT. It adds 67 tokens to every session and 686 once invoked, about $0.0003 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-30.
Other skills, from other repositories
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.
autotask-creator
Rules for automation CRUD from the group-chat commander. The commander does not call mutation tools and does not edit cloud/autotasks files directly. It emits one or more top-level ... containers in its final text; the bus parses and applies them after the turn.
remove
Remove a deployed framework or addon from the current workspace.
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…
magpie-security-issue-import-from-md
Open one or more tracking issues from a markdown file containing a batch of security findings. Each finding becomes one tracker landing in the Needs triage board column. The file itself is the full report — there is no inbound reporter to reply to and no PR to inspect.