Borrowing it
Nothing to install: this file belongs to kylemabry95/intervals.icu_to_claude_mcp_connection. 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/kylemabry95/intervals.icu_to_claude_mcp_connection/main/.github/agents/speckit.taskstoissues.agent.mdgit clone --depth 1 https://github.com/kylemabry95/intervals.icu_to_claude_mcp_connectionWrote 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/agents/kylemabry95/intervals.icu_to_claude_mcp_connection/speckit.taskstoissues)<a href="https://agentmods.dev/agents/kylemabry95/intervals.icu_to_claude_mcp_connection/speckit.taskstoissues"><img src="https://agentmods.dev/badge/agents/kylemabry95/intervals.icu_to_claude_mcp_connection/speckit.taskstoissues/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/agents/kylemabry95/intervals.icu_to_claude_mcp_connection/speckit.taskstoissues"><img src="https://agentmods.dev/badge/agents/kylemabry95/intervals.icu_to_claude_mcp_connection/speckit.taskstoissues.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.00021 | $0.00940 |
| Opus 5 | $0.00010 | $0.00470 |
| Sonnet 5 | $0.00004 | $0.00188 |
| Haiku 4.5 | $0.00002 | $0.00094 |
Grade A, and why
speckit.taskstoissues 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.
This is a copy
97% identical to speckit.taskstoissues — 1 line differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 98 lines — stays where its author put it; the contents beside it link to each section on GitHub.
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
Pre-Execution Checks
Check for extension hooks (before tasks-to-issues conversion):
- Check if
.specify/extensions.ymlexists in the project root. - If it exists, read it and look for entries under the
hooks.before_taskstoissueskey - If the YAML cannot be parsed or is invalid, skip hook checking silently and continue normally
- Filter out hooks where
enabledis explicitlyfalse. Treat hooks without anenabledfield as enabled by default. - For each remaining hook, do not attempt to interpret or evaluate hook
conditionexpressions:- If the hook has no
conditionfield, or it is null/empty, treat the hook as executable - If the hook defines a non-empty
condition, skip the hook and leave condition evaluation to the HookExecutor implementation
- If the hook has no
- For each executable hook, output the following based on its
optionalflag:- Optional hook (
optional: true):## Extension Hooks **Optional Pre-Hook**: {extension} Command: `/{command}` Description: {description} Prompt: {prompt} To execute: `/{command}` - Mandatory hook (
optional: false):## Extension Hooks **Automatic Pre-Hook**: {extension} Executing: `/{command}` EXECUTE_COMMAND: {command} Wait for the result of the hook command before proceeding to the Outline.
- Optional hook (
- If no hooks are registered or
.specify/extensions.ymldoes not exist, skip silently
Outline
- Run
.specify/scripts/bash/check-prerequisites.sh --json --require-tasks --include-tasksfrom repo root and parse FEATURE_DIR and AVAILABLE_DOCS list. All paths must be absolute. For single quotes in args like "I'm Groot", use escape syntax: e.g 'I'''m Groot' (or double-quote if possible: "I'm Groot"). - IF EXISTS: Load
.specify/memory/constitution.mdfor project principles and governance constraints. - From the executed script, extract the path to tasks.
- Get the Git remote by running:
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 · 98 lines · 21 tokens per session scan A 6fb1d3f1b666
speckit.taskstoissues is an agent published in the GitHub repository kylemabry95/intervals.icu_to_claude_mcp_connection (0 stars, last pushed 2mo ago), licensed MIT. It adds 21 tokens to every session and 940 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. It is 97% identical to speckit.taskstoissues, differing in 1 line, and is treated as a copy.
Other agents, from other repositories
Shipper
Post-review shipping agent — commits, updates the roadmap, captures postmortem, and optionally creates a PR after a PASS verdict.
iris
GitHub operations specialist — branches, pull requests, issues, releases, tags. Called by zeus after review. Never pushes or merges without explicit human approval. Integrates with VS Code GitHub Pull Requests extension.
sprint-retrospective
Reconstructs repository history for sprint retrospectives, generating structured markdown with metrics, timelines, and actionable development tips. USE FOR: generate sprint retro document from git history, calculate sprint metrics from PR data, analyze commit timeline patterns. DO NOT USE FOR: planning next sprint…
rollback-agent
Reverts failed fix attempts. Resets git state and posts block comment to issue tracker.
delivery-lead
Delivery team lead. Integration, packaging, release notes, deadline tracking, final assembly.
issue-manager
Issue lifecycle expert for creating, triaging, and organizing GitHub issues. Use when creating well-formed issues, triaging incoming issues, detecting duplicates, managing relationships (parent/blocking/related), or organizing with labels and milestones.