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 gohypergiant/agent-skills --skill accelint-qrspi-proposegit clone --depth 1 https://github.com/gohypergiant/agent-skillsWrote 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/gohypergiant/agent-skills/accelint-qrspi-propose)<a href="https://agentmods.dev/skills/gohypergiant/agent-skills/accelint-qrspi-propose"><img src="https://agentmods.dev/badge/skills/gohypergiant/agent-skills/accelint-qrspi-propose/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/gohypergiant/agent-skills/accelint-qrspi-propose"><img src="https://agentmods.dev/badge/skills/gohypergiant/agent-skills/accelint-qrspi-propose.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 2 findings, up to medium
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- medium Excessive Agency · line 69 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
- medium Excessive Agency · line 738 Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
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.00180 | $0.09293 |
| Opus 5.5 | $0.00072 | $0.03717 |
| Sonnet 5.5 | $0.00036 | $0.01859 |
| Haiku 4.5 | $0.00018 | $0.00929 |
Grade A, and why
accelint-qrspi-propose 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 12d 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 — 737 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Accelint QRSPI
Automate the QRSPI + OpenSpec planning workflow. This skill applies the methodology from "We Got RPI Wrong" through OpenSpec's artifact system. It orchestrates the Questions → Research → Design → Structure stages and requires human checkpoints before any code is written.
What This Skill Does
Automates: The planning phase of spec-driven development using QRSPI Scope: Questions → Research → Design → Structure/Plan (stops before implementation) Output: A complete OpenSpec change ready for the accelint-qrspi-apply skill
Does NOT: Implement code, run tests, create PRs, or archive changes
Prerequisites
This skill requires the expanded OpenSpec workflows (explore, new, continue) to access the step-by-step artifact generation.
To verify these workflows are enabled:
openspec config list
Check that the workflows: section includes: explore, new, and continue.
If any are missing, enable the expanded profile:
openspec config profile
# Select "expanded" from the list
openspec update
Workflow Overview
┌──────────────────────────────────────────────────────────────────┐
│ Stage Context Output Checkpoint │
├──────────────────────────────────────────────────────────────────┤
│ Questions Ticket only Questions — │
│ Research Questions only Research doc — │
│ Design Q+R (NO ticket) proposal.md — │
│ design.md — │
│ [STOP HERE] │
│ ⚠️ CHECKPOINT 1: Review proposal.md + design.md - MUST approve │
│ (frontmatter: specs_touched/decisions/created_at -> design.md) │
│ │
│ Specs/Tasks Q+R+design tasks.md — │
│ (specs/* is OpenSpec bookkeeping; generated whenever OpenSpec │
│ decides, not reviewed) │
│ ⚠️ CHECKPOINT 2: Review tasks.md - MUST approve to continue │
│ │
│ Done — Exit — │
└──────────────────────────────────────────────────────────────────┘
Note: Keep the ticket OUT of context after the Questions stage to prevent completion bleed.
REQUIRED: The Design stage (steps 17-26) must produce `proposal.md` and `design.md` and stops before `tasks.md` (OpenSpec may also generate `specs/*` along the way, in whatever order it chooses), optionally creates `trace.md` if the `--verbose` flag was set, then STOPS for review at step 27. The Specs/Tasks stage (steps 33-43) generates `tasks.md` (and `specs/*` if not already present) separately after design approval.
Steps keep their numbers and carry stable tags (for example `[CHECKPOINT-1]`) so references stay unambiguous: `[S-QUESTIONS]` (8), `[S-RESEARCH]` (13), `[S-DESIGN-GEN]` (17), `[CHECKPOINT-1]` (27), `[S-FRONTMATTER]` (31), `[S-TASKS-GEN]` (33), `[CHECKPOINT-2]` (44).
Capture frontmatter at step 31 after Checkpoint 1 approval, not before. `design.md` reaches its final form for this planning pass only after the user approves it or confirms a manual edit. Earlier capture can write `specs_touched/decisions/created_at` against content the user is about to change. The `created_at` timestamp marks when the user approved the design (the moment the change becomes "real").
⚠️ REQUIRED CHECKPOINTS: The agent MUST pause and wait for explicit user approval at both checkpoints (step 27 [CHECKPOINT-1] and step 44 [CHECKPOINT-2]). Proceeding without approval bypasses QRSPI's core value.
What ships with it
3 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.
- 12d ago Changed · -11 lines ab2836ec5e68
- 1mo ago Changed 32eedbfeccdc
- 1mo ago Changed · +66 lines 51fb2b014a2c
- 1mo ago First seen · 682 lines · 180 tokens per session scan A 7bca4b47f74f
accelint-qrspi-propose is a skill published in the GitHub repository gohypergiant/agent-skills (25 stars, last pushed 9d ago), licensed Apache-2.0. It adds 180 tokens to every session and 9,293 once invoked, about $0.0007 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
story-readiness
Checks whether a story is ready to implement: clear acceptance criteria, no open questions, valid ADR and dependencies. Use when the user asks if a story, or the sprint's stories, are ready to start or build.
recipe-create-meet-space
Create a Google Meet meeting space and share the join link.
workthreads
SpecStory Workthreads - a weekly work-thread rollup across a team's repos from SpecStory coding histories (any agent - Claude Code, Codex, Cursor, Gemini, and more). It groups the window's sessions into threads of work per project and labels each new / open / recently closed, so a lead sees what shipped, what is still…
atmos-config
Atmos root configuration: atmos.yaml discovery, precedence, deep merging, basepath, imports, minimal bootstrap, and routing to narrower Atmos skills.
qa-project-bootstrap
Onboard a new QA engineer to an existing codebase, or audit an existing test architecture. Produces a 30-day ramp plan: codebase orientation, framework walkthrough, test architecture audit, mentorship pairing, and first-test guidance. Use when: "QA onboarding," "new tester," "ramp up," "test architecture audit,"…
remove
Remove a deployed framework or addon from the current workspace.