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 build-with-dhiraj/ai-workflow-framework-portability-kit --skill jove-ticket-graphgit clone --depth 1 https://github.com/build-with-dhiraj/ai-workflow-framework-portability-kitWrote 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/build-with-dhiraj/ai-workflow-framework-portability-kit/jove-ticket-graph)<a href="https://agentmods.dev/skills/build-with-dhiraj/ai-workflow-framework-portability-kit/jove-ticket-graph"><img src="https://agentmods.dev/badge/skills/build-with-dhiraj/ai-workflow-framework-portability-kit/jove-ticket-graph/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/build-with-dhiraj/ai-workflow-framework-portability-kit/jove-ticket-graph"><img src="https://agentmods.dev/badge/skills/build-with-dhiraj/ai-workflow-framework-portability-kit/jove-ticket-graph.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.00078 | $0.00591 |
| Opus 5.5 | $0.00031 | $0.00236 |
| Sonnet 5.5 | $0.00016 | $0.00118 |
| Haiku 4.5 | $0.00008 | $0.00059 |
Grade A, and why
jove-ticket-graph 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.
What it actually says
JoVE ticket graph
On-demand deep-read. Close, stay, or split is optional and comes last.
Project root is ~/dev/jove-hq. Read REFERENCE.md for prune rules, Slack hops, attachments, and JVA Closed vs Done.
Do not copy CLAUDE.md rule 14. This skill feeds it. Do not use jove-scope-audit for this: that walk is one hop and registry-only.
Run
- State the seed key. Say you are walking, not acting.
- Print the graph before reading bodies:
node ~/dev/jove-hq/.claude/skills/jove-ticket-graph/scripts/walk.mjs --seed <KEY>Exit 2 (no Jira token): BFS yourself withgetJiraIssueissuelinksusing the same FOLLOW / SKIP / mega-epic rules. Do not invent a shorter walk.--selftestmust pass either way. - Every printed key, every hop: description, all comments, all attachments. Cite or abstain per file.
- Slack hops 1 to 3 from those keys and named people. Read threads to the end. A reply outranks its parent (
jove-connectors.md). - Calls and email only when a ticket or thread names them. Full transcript or full thread.
- Write
~/dev/jove-hq/knowledge/jove-labs/STITCH-<key>-<YYYY-MM-DD>.mdwith## Sources, in order. Classify each item: decides vs covers. Newest decision governs. An older piece still binds what it alone governs. Conflict: keep both and name the question. - Stop. If asked for an end action, recommend close / same ticket / follow-on from the stitch. Humanizer and egress lint only if something leaves the vault.
Hard stops
- Depth 3 is a ceiling, not a target to exceed.
- Do not enumerate an epic's children. Record the epic as a leaf.
- Do not draft, comment, or book before the stitch exists.
- Do not Slack-draft the stitch.
Specimen
JVA-31344: hop 2/3 held the 30-day policy (JVA-19543, JVA-25045, JVA-25851). The CSV was an attachment. The group DM was not on the ticket.
What ships with it
2 files 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.
- 1mo ago First seen · 36 lines · 78 tokens per session scan A 3e0827c5d890
jove-ticket-graph is a skill published in the GitHub repository build-with-dhiraj/ai-workflow-framework-portability-kit (5 stars, last pushed 21d ago), licensed MIT. It adds 78 tokens to every session and 591 once invoked, about $0.0003 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-09-21.
Other skills, from other repositories
feature-dev
Guide a feature implementation through a structured seven-phase workflow with deep codebase understanding, clarifying questions, parallel architecture design, and quality review. Use this skill when the user asks to build a new feature, add functionality, or wants a methodical approach to implementation rather than…
work-log-claude
A work-log generator that reads Claude Code's local session records and produces an evidence-based Markdown report. It can organise work by project and time period while excluding unrelated session data.
prd-executor
Triggers when: user says "start executing PRD", "start development", "execute breakdown", "implement REQ", or a Dev Agent is assigned to a breakdown directory under docs/. Use this skill to guide the execution of a prddecomposer breakdown from start to finish, enforcing hard gates on requirements confirmation, TDD…
wayfinder
Plan a huge chunk of work — more than one agent session can hold — as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
openspec-bulk-archive-change
Archive multiple completed changes at once. Use when archiving several parallel changes.
triage
Move issues and external PRs through a state machine of triage roles — categorise, verify, grill if needed, and write agent-ready briefs.