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 LuisFelipeMoro/Harness-devkit --skill analysisgit clone --depth 1 https://github.com/LuisFelipeMoro/Harness-devkitWrote 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/luisfelipemoro/harness-devkit/analysis)<a href="https://agentmods.dev/skills/luisfelipemoro/harness-devkit/analysis"><img src="https://agentmods.dev/badge/skills/luisfelipemoro/harness-devkit/analysis/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/luisfelipemoro/harness-devkit/analysis"><img src="https://agentmods.dev/badge/skills/luisfelipemoro/harness-devkit/analysis.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.00082 | $0.00464 |
| Opus 5.5 | $0.00033 | $0.00186 |
| Sonnet 5.5 | $0.00016 | $0.00093 |
| Haiku 4.5 | $0.00008 | $0.00046 |
Grade A, and why
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 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
Run the analysis phase (Analyst + PM only). If no task is provided, ask first.
Load agent files on demand — never pre-load both at once. Use references/output-format.md section headers for all agent output.
Scope: requirements analysis only — no architecture decisions, no Language column, no sub-task decomposition. To create an execution plan from this output, run
/planning. To implement end-to-end (includes planning), run/multi-agent.
Step 1 — Analyst (Mary)
Load agents/analyst.md. Run against the task description.
- Include: language context, security constraints, business goals
- Output:
docs/deliveries/{key}/product-brief.md(show in full) — derive the slug + key from the feature name perreferences/delivery-and-worktree.md; a root-levelproduct-brief.mdwould be clobbered by the next delivery
Step 2 — PM (John)
Load agents/pm.md. Run against the Brief from Step 1.
- Security ACs are mandatory for any I/O, auth, or data-handling epic
- Output:
docs/deliveries/{key}/PRD.md(show in full)
Step 3 — Epic Summary
Extract every epic from the PRD and display the Epic Summary:
| Epic | Tasks | Acceptance Criteria | Security ACs |
|---|---|---|---|
| Epic N: {title} | T{N}.1: {imperative}, T{N}.2: … | AC1, AC2, … | SEC-1, … (or —) |
After showing the summary, print the closing block from references/output-contract.md.
What ships with it
1 file 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 Changed · -7 lines · +44 tokens per session 6994f9233283
- 1mo ago First seen · 49 lines · 38 tokens per session scan A 11e5ad041ec2
analysis is a skill published in the GitHub repository LuisFelipeMoro/Harness-devkit (13 stars, last pushed today), licensed MIT. It adds 82 tokens to every session and 464 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-08-31.
Other skills, from other repositories
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chronicle
Analyze Copilot session history for standup reports, usage tips, session search, and session reindexing. Use when the user asks for a standup, daily summary, usage tips, workflow recommendations, wants to search or find past sessions by keyword/file/PR, wants to reindex their session store, or asks about deleting…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
component-fixtures
Use when creating or updating component fixtures for screenshot testing or their shared infrastructure, or when designing UI components to be fixture-friendly. Covers fixture file structure, theming, service setup, CSS scoping, async rendering, validation, and common pitfalls.