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 loiane/specs-driven-development-spring-angular --skill issue-tracker-ingestiongit clone --depth 1 https://github.com/loiane/specs-driven-development-spring-angularWrote 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/loiane/specs-driven-development-spring-angular/issue-tracker-ingestion)<a href="https://agentmods.dev/skills/loiane/specs-driven-development-spring-angular/issue-tracker-ingestion"><img src="https://agentmods.dev/badge/skills/loiane/specs-driven-development-spring-angular/issue-tracker-ingestion/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/loiane/specs-driven-development-spring-angular/issue-tracker-ingestion"><img src="https://agentmods.dev/badge/skills/loiane/specs-driven-development-spring-angular/issue-tracker-ingestion.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.00053 | $0.00765 |
| Opus 5.5 | $0.00021 | $0.00306 |
| Sonnet 5.5 | $0.00011 | $0.00153 |
| Haiku 4.5 | $0.00005 | $0.00076 |
Grade A, and why
issue-tracker-ingestion 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 1mo 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 — 77 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue tracker ingestion
Supported sources
| Source | MCP server | Identifier shape |
|---|---|---|
| Jira (Atlassian) | atlassian |
SHOP-1422 |
| GitHub Issues | github |
owner/repo#42 or URL |
| GitHub Pull Requests | github |
owner/repo!42 or URL |
| Linear | linear |
ENG-123 |
| Azure Boards | azure-devops |
AB#54321 |
If no MCP is configured, fall back to user-provided text. Never invent a ticket.
Recipe (per source)
-
Resolve identifier → MCP fetch.
-
Capture: title, description, status, labels, assignee, comments (last 10), attachments (filenames only), URL, fetched-at timestamp.
-
Write a verbatim block in
01-spec.md:## Source - **System:** Jira - **ID:** SHOP-1422 - **URL:** https://example.atlassian.net/browse/SHOP-1422 - **Title:** Apply gift card at checkout - **Status:** In Progress - **Fetched:** 2026-04-18T10:00:00Z ### Description (verbatim) > Users should be able to apply a gift card during checkout. It should reduce the order total. If the card has been used, show an error. ### Comments (last N, verbatim) > [PM, 2026-04-15]: Confirmed only authenticated buyers in scope. > [Eng lead, 2026-04-16]: Use existing error envelope. -
Extract candidate ACs only from the verbatim text. Do not paraphrase requirements; quote the source line and put your AC under it. If a candidate AC has no source line, it goes to
## Open Questionsas aQ-NNN.
No-invention enforcement
If a source field is missing (e.g. no acceptance criteria in the ticket), the agent does not fill it from imagination. It writes:
- **Q-001** — Source ticket has no explicit acceptance criteria. Need user to confirm AC list before proceeding to AC drafting.
/spec then halts and asks the user.
Updating after the ticket changes
If the user re-runs /spec and the ticket has changed:
- Re-fetch.
- Diff old vs new in
## Out-of-Band Inputs("ticket updated 2026-04-19; description gained paragraph about partial redemption"). - Add
Q-NNNfor any new requirement not yet in AC.
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.
- 1mo ago First seen · 77 lines · 53 tokens per session scan A 4d088470bf49
issue-tracker-ingestion is a skill published in the GitHub repository loiane/specs-driven-development-spring-angular (62 stars, last pushed 11d ago), licensed MIT. It adds 53 tokens to every session and 765 once invoked, about $0.0002 per session on Opus 5.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
spec-kitty-implement-review
Orchestrate the implement-review loop for Spec Kitty work packages using any configured agent. Covers agent dispatch, state transitions, rejection cycles, arbiter escalation, and dependency-aware sequencing across all 13 supported coding agents. Triggers: "implement and review WPs", "run the implement-review loop"…
spec-kitty-mission-system
Understand how Spec Kitty missions work: the 4 built-in mission types, how they define workflows via step contracts and action indices, how missions and work packages relate, how templates are resolved through the 6-tier chain, and how doctrine artifacts (procedures, tactics, directives) compose mission behavior.…
spec-kitty-program-orchestrate
Orchestrate a multi-repo, multi-mission Spec Kitty program end-to-end: run specify → plan → tasks → implement → review → merge → mission-review → post-merge fixes across several repositories in a defined dependency order, using background sub-agents for parallel work and a pulse-heartbeat safety net for long…
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…
spk-run-verdict-capture
Set a Spec Kitty work-package review verdict through the deterministic event-log seam, so every agent harness records approve/reject the same way.
spk-run-implement-review
Orchestrate Spec Kitty work-package implementation and review loops until all packages are done, approved, or correctly rejected.