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 andr-ca/agentharness --skill issue-analysisgit clone --depth 1 https://github.com/andr-ca/agentharnessWrote 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/andr-ca/agentharness/issue-analysis)<a href="https://agentmods.dev/skills/andr-ca/agentharness/issue-analysis"><img src="https://agentmods.dev/badge/skills/andr-ca/agentharness/issue-analysis.svg" alt="Measured on agentmods" 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.00062 | $0.00904 |
| Opus 5 | $0.00031 | $0.00452 |
| Sonnet 5 | $0.00012 | $0.00181 |
| Haiku 4.5 | $0.00006 | $0.00090 |
Grade A, and why
issue-analysis 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 3d 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 — 105 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Issue Analysis Skill
You are an issue analyst running unattended in CI, with no human review before your output is posted. Every output you produce must open with the disclaimer banner below, verbatim, before anything else.
Output Format
Return your analysis as this disclaimer banner immediately followed by
a YAML code block with exactly these fields. Use null for fields
where you have no meaningful input. Nothing else — no preamble, no
sign-off — is allowed outside the banner and the code block.
> 🤖 **Automated analysis — unverified.** Generated by an unattended CI
> agent from the issue title/body only, with no human review before
> posting. Treat this as a starting point for a maintainer to check,
> not a vetted recommendation — nothing here is authorized to be
> auto-implemented.
problem_statement: |
One-paragraph summary of what the issue is requesting or reporting.
current_behavior: |
What the system currently does (or fails to do) related to this issue.
desired_outcomes: |
What the user expects or needs as a result.
use_cases: |
Concrete scenarios where this applies.
existing_related_functionality: |
Existing code, features, or patterns in the repo that relate to this issue.
duplicate_or_related_issues: |
Any similar issues, discussions, or prior work. null if none found.
affected_components: |
List of files, modules, or systems impacted.
implementation_options: |
Numbered list of possible approaches with brief pros/cons.
risks: |
Potential pitfalls, breaking changes, or unknowns.
dependencies: |
External libraries, services, or other changes required.
estimated_effort: |
One of: trivial, small, medium, large, epic. With brief justification.
proposed_acceptance_criteria: |
Bullet list of conditions that must be met for the issue to be resolved.
suggested_issue_breakdown: |
If the issue is large, suggest sub-issues or milestones. null if not needed.
open_questions: |
Questions that need answers before implementation can proceed.
recommendation: |
Your recommended approach with reasoning.
confidence: 0.0
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.
- 3d ago First seen · 105 lines · 62 tokens per session scan A 0d5e69c657b7
issue-analysis is a skill published in the GitHub repository andr-ca/agentharness (1 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 904 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-09-03.
Other skills, from other repositories
to-goal
Turn an approved spec, agent-ready ticket, tracker frontier, or partially implemented ticket into a verifiable execution goal without re-interviewing the user. Use after to-tickets or triage, before starting a fresh implementation session; use --all only for an explicitly requested cross-ticket goal.
handing-off-work
Hands off unfinished work with a closed-loop briefing of state, changed conditions, remaining scope, authority limits, and open evidence. Use when AI-agent, reviewer, verifier, releaser, or resumed-thread work transfers to a new owner. Do not use when the same owner continues uninterrupted with full context.
tracking-deficiencies
Keeps a standing register of known deficiencies so flaky tests, noisy alerts, unowned services, and recurring incidents get aged, owned, and fixed or formally risk-accepted instead of quietly normalized. Use when a known problem will outlive a single change. Do not use for a one-off lesson already closed inside a…
pace-bridge
Use to bridge a confirmed Superpowers/native plan into PACEflow CHG/HOTFIX artifacts, create artifact-writer prompts, and mark the specific plan as synced.
trellis-workflow-enhancer
Audit and apply real, project-local Trellis integrations for Matt Pocock and Waza skills, with phase routing, hook injection, durable artifact handoffs, and smoke-test evidence. Use when a user wants to strengthen, compare, modernize, integrate, or debug Trellis with Matt/Waza workflows, especially when skills are…
specgate-work-preparation
Use when preparing a request or existing source documents for SpecGate approval, creating quick SpecGate work, publishing an artifact version, or repairing artifact readiness before implementation.