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 wangke19/gemini-ai-helpers --skill create-taskgit clone --depth 1 https://github.com/wangke19/gemini-ai-helpersWrote 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/wangke19/gemini-ai-helpers/create-task)<a href="https://agentmods.dev/skills/wangke19/gemini-ai-helpers/create-task"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/create-task/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/wangke19/gemini-ai-helpers/create-task"><img src="https://agentmods.dev/badge/skills/wangke19/gemini-ai-helpers/create-task.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.00015 | $0.03816 |
| Opus 5 | $0.00008 | $0.01908 |
| Sonnet 5 | $0.00003 | $0.00763 |
| Haiku 4.5 | $0.00002 | $0.00382 |
Grade B, and why
Create Jira Task scanned grade B with 1 finding 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 7d 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.
Strips warnings and disclaimersmediumAnti-refusal
Omitting safety caveats hides risk from the user and is a common jailbreak preamble.
- Documentation builds without warnings How it starts
The opening of the file, as written. The whole thing — 623 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Create Jira Task
This skill provides implementation guidance for creating Jira tasks, which are used for technical or operational work that doesn't necessarily deliver direct user-facing value.
When to Use This Skill
This skill is automatically invoked by the /jira:create task command to guide the task creation process.
Prerequisites
- MCP Jira server configured and accessible
- User has permissions to create issues in the target project
- Understanding of the technical work to be performed
Reference Documentation:
- Markdown for Jira Reference - Markdown formatting for Jira descriptions
- MCP Tools Reference - MCP tool signatures and custom fields
- CLI Fallback Reference - jira-cli commands (only if MCP unavailable)
Tasks vs Stories
When to Use a Task
Use a Task when the work is:
- Technical/operational - Infrastructure, refactoring, configuration
- Not user-facing - No direct end-user functionality
- Internal improvement - Code quality, performance, maintenance
- Enabler work - Supports future stories but isn't user-visible
Examples of tasks:
- "Update scaling documentation"
- "Refactor authentication utility package"
- "Configure CI pipeline for integration tests"
- "Upgrade dependency X to version Y"
- "Investigate performance regression in component Z"
When to Use a Story Instead
Use a Story when the work:
- Delivers user-facing functionality
- Can be expressed as "As a... I want... so that..."
- Has business value to end users
- Is part of a user workflow
If in doubt: Ask "Would an end user notice or care about this change?"
- Yes → Story
- No → Task
Task Best Practices
Clear Summary
The summary should:
- Be concise (one sentence)
- Use action verbs (Update, Refactor, Configure, Investigate, Fix)
- Identify what is being changed
- Optionally include "why" if not obvious
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.
- 7d ago First seen · 623 lines · 15 tokens per session scan B d0761c5ba0ec
Create Jira Task is a skill published in the GitHub repository wangke19/gemini-ai-helpers (2 stars, last pushed 5mo ago), licensed Apache-2.0. It adds 15 tokens to every session and 3,816 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it B with 1 finding (strips warnings and disclaimers). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.
Other skills, from other repositories
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-team-sync
Operate Spec Kitty tracker sync (sync pull/sync push/sync run for local providers) and hosted SaaS-backed mission data.
spk-run-program-orchestrate
Orchestrate multi-repo, multi-mission Spec Kitty programs across dependencies, parallel agents, review gates, merge, and post-merge closeout.
spk-gate-retrospective
Create or verify Spec Kitty mission retrospectives after merge and surface process learnings without blocking completed work.
lov-gh-tidy
Interactive GitHub repo hygiene skill. Lists all open issues, PRs, stale branches, and orphan labels, shows a summary of each with analysis, then asks the user how to handle each item (close, merge, comment, delete, keep). Executes all chosen actions via gh CLI. Use when the user says "清理 GitHub", "tidy repo", "clean…
cc-skill-project-guidelines-example
Project Guidelines Skill (Example).