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 mostafa-drz/claude-skills --skill thread-to-actiongit clone --depth 1 https://github.com/mostafa-drz/claude-skillsWrote 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/mostafa-drz/claude-skills/thread-to-action)<a href="https://agentmods.dev/skills/mostafa-drz/claude-skills/thread-to-action"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/thread-to-action/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/mostafa-drz/claude-skills/thread-to-action"><img src="https://agentmods.dev/badge/skills/mostafa-drz/claude-skills/thread-to-action.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.00054 | $0.01308 |
| Opus 5 | $0.00027 | $0.00654 |
| Sonnet 5 | $0.00011 | $0.00262 |
| Haiku 4.5 | $0.00005 | $0.00131 |
Grade A, and why
thread-to-action 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 — 178 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Thread → Action
Analyze a pasted conversation thread and suggest concrete developer actions, then execute them with confirmation.
Preferences
Read ~/.claude/skills/thread-to-action/preferences.md using the Read tool. If not found, no preferences are set.
Context
On startup, use Bash to detect: current git branch, recent commits (git log --oneline -5), git status, and open PRs (gh pr list --author @me --state open --limit 5). Skip any that fail.
Command routing
Check $ARGUMENTS:
help→ display help then stopconfig→ interactive setup then stopreset→ delete~/.claude/skills/thread-to-action/preferences.md, confirm, stop- anything else → process as thread
Help
Thread → Action — Parse a thread and suggest developer actions
Usage:
/thread-to-action <paste thread> Analyze and suggest actions
/thread-to-action config Configure context sources and action types
/thread-to-action reset Clear preferences
/thread-to-action help This help
Context sources:
Git: branch, recent commits, status, open PRs
Linear: active issues, recent issues assigned to me
Session: working directory, CLAUDE.md, prior conversation
Action types: Git/PR, Linear, Code, Cleanup
See reference/action-types.md for full list
Current preferences:
(shown above under Preferences)
Config
Use AskUserQuestion:
Q1 — "Which context sources should be active?" (multiSelect: true)
- Git context (branch, commits, status, PRs)
- Linear context (active issues, recent issues)
- Session context (working directory, CLAUDE.md)
Q2 — "Default Linear filters?" (multiSelect: false)
- Use my assignments (default)
- Use specific team/project
- No Linear filtering
Q3 — "Which action types to suggest?" (multiSelect: true)
- Git/PR actions
- Linear actions
- Code actions
- Cleanup actions
Save to ~/.claude/skills/thread-to-action/preferences.md.
First-time detection
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 Changed · +3 lines 87ec17fab0e8
- 12d ago First seen · 175 lines · 54 tokens per session scan A 7658a02cd324
thread-to-action is a skill published in the GitHub repository mostafa-drz/claude-skills (4 stars, last pushed today), licensed MIT. It adds 54 tokens to every session and 1,308 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-31.
Other skills, from other repositories
codex-symphony
Install and operate a portable OpenAI Symphony + Linear orchestration setup in any Git repository. Use when the user wants a one-command local Symphony runner, a reusable WORKFLOW template, background launch scripts, or a Codex wrapper that restarts Symphony automatically when reopening the CLI.
timeline-creator
Create HTML timelines and project roadmaps with Gantt charts, milestones, phase groupings, and progress indicators. Use when users request timelines, roadmaps, Gantt charts, project schedules, or milestone visualizations.
daily-working
End-to-end pipeline: pull a task from the project's task tracker by ID (Redmine or GitHub Issues today, more addable via a new adapter), sanity-check and impact-assess it against the codebase before touching anything, implement it with the Claude CLI, verify the result in a real browser via the Claude Chrome extension…
shipkit-user-instructions
Use when there are manual tasks the user must complete. Triggers: 'create task', 'track TODO', 'user needs to', 'manual step required'.
caregiver-coordination
Analyze caregiver coordination platforms for scheduling optimization, task assignment, handoff communication, family/professional caregiver integration, care plan compliance, burnout prevention, and documentation workflows..
disability-services
Analyze disability services software — IEP and ISP management, person-centered planning workflows, HCBS Settings Rule compliance, accommodation tracking, assistive technology integration, EVV (Electronic Visit Verification), caregiver and DSP scheduling, and outcome measurement.