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 agentmods add skills/foliveira/harmonia/rejectnpx skills add foliveira/harmonia --skill rejectgit clone --depth 1 https://github.com/foliveira/harmoniaWrote 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/foliveira/harmonia/reject)<a href="https://agentmods.dev/skills/foliveira/harmonia/reject"><img src="https://agentmods.dev/badge/skills/foliveira/harmonia/reject.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 | $0.00039 | $0.00255 |
| Opus 5 | $0.00019 | $0.00128 |
| Sonnet 5 | $0.00008 | $0.00051 |
| Haiku 4.5 | $0.00004 | $0.00026 |
Grade A, and why
reject 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 4d 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
This is a human-invoked touchpoint. Rejection is a human act: no other skill or agent - flow explicitly - runs it or bash ${CLAUDE_PLUGIN_ROOT}/bin/workspace.sh reject on the developer's behalf.
--reason <text> is required - a reason-less rejection carries no signal. Ask the developer for the reason if they did not give one, then run:
bash ${CLAUDE_PLUGIN_ROOT}/bin/workspace.sh reject --repo . --reason "<the developer's reason>"
Surface the script's output verbatim. The script is the single source of truth - it resolves the workspace, guards the base ref, supersedes any prior acceptance, and writes the rejected marker (timestamp, reason, diff digest). A live rejection blocks /harmonia:capture through verify-acceptance until the developer re-accepts (which supersedes it) or abandons the task. Do not fork its logic.
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.
- 4d ago First seen · 16 lines · 39 tokens per session scan A 6f3bbeae5c61
reject is a skill published in the GitHub repository foliveira/harmonia (2 stars, last pushed 19d ago), licensed MIT. It adds 39 tokens to every session and 255 once invoked, about $0.0002 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-08-31.
Other skills, from other repositories
todos
This chat has a shared, live TODO plan — your tasks for the conversation, which the user also edits. Read this skill and reach for the todo tools whenever a request takes more than a couple of steps. It covers the plan model (group = task, items = its steps; loose items are the user's lane), how to work it: propose…
writing-workflow-skills
Use when adding a new workflow skill to pi-thinkrail-workflow, changing an existing workflow skill's role, trigger, handoff, or structure, or checking a workflow skill against the workflow system's rules. Not for authoring general-purpose skills outside this package.
writing-specs
Use when a workflow step drafts or revises a spec artifact — a goal-and-requirements, an architecture, or a module SPEC — or when a workflow skill names it at such a step. The shared quality bar for specs — not a workflow, nothing to execute.
clarify
Adaptive requirements clarification with auto-depth routing. Shallow (Q&A) for simple tasks, Deep (exploration + DRAFT + PLAN) for complex ones. Escalates automatically when ambiguity persists.
auditing-aws-s3-bucket-permissions
Systematically audit AWS S3 bucket permissions to identify publicly accessible buckets, overly permissive ACLs, misconfigured bucket policies, and missing encryption settings using AWS CLI, S3audit, and Prowler to enforce least-privilege data access controls.
containing-active-breach
Executes containment strategies to stop active adversary operations and prevent lateral movement during a confirmed security breach. Implements short-term and long-term containment using network segmentation, endpoint isolation, credential revocation, and access control modifications. Activates for requests involving…