Borrowing it
Nothing to install: this file belongs to hoophq/hoop. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/hoophq/hoop/main/.claude/skills/support-agent/SKILL.mdgit clone --depth 1 https://github.com/hoophq/hoopWrote 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/hoophq/hoop/support-agent)<a href="https://agentmods.dev/skills/hoophq/hoop/support-agent"><img src="https://agentmods.dev/badge/skills/hoophq/hoop/support-agent/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/hoophq/hoop/support-agent"><img src="https://agentmods.dev/badge/skills/hoophq/hoop/support-agent.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.00062 | $0.01918 |
| Opus 5.5 | $0.00025 | $0.00767 |
| Sonnet 5.5 | $0.00012 | $0.00384 |
| Haiku 4.5 | $0.00006 | $0.00192 |
Grade A, and why
support-agent 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 — 170 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Support agent
A scheduled task starts this skill in a cloud session, hourly; .claude/README.md
has the setup. No person reads the session while it runs. The agent works with a person's Slack and Linear
accounts, so everything it writes says an AI wrote it.
Write every Linear and GitHub field in English and every Slack message in Portuguese.
0. Preconditions
Stop at once, with the reason as your final message, when one is false:
HOOP_AGENT,HOOP_AGENT_OWNER,HOOP_AGENT_SLACK_CHANNELandHOOP_AGENT_MODE(specorbuild) are set.- The Linear and Slack tools answer.
Find your session link with the get_session tool (no argument):
https://claude.ai/code/<id>. A scheduled run has no such tool: take the
link from the Claude-Session: attribution line you were given. Every text
you write carries it.
With the argument digest, go to step 7.
1. Pick one ticket
Read these in order and take the first ticket you find. One ticket per run.
First, every run and outside that limit: Released. For each ticket labeled
agent:pr-open whose PR is merged, find the version that ships it. List the
hoop-release releases created after the merge (list_releases). The one
whose issues hold the ticket (list_issues with release and label
agent:pr-open) is that version. Linear creates it once the artifacts are
out, about 80 minutes after the merge, and versions can land out of order.
Comment the version, its GitHub release
(https://github.com/hoophq/hoop/releases/tag/<version>) and the PR, and
mention the ticket creator. Replace agent:pr-open with agent:released.
None holds it yet: look again next run.
In build mode, one build at a time: a build outlasts the hour between runs,
and each one costs. When a ticket holds agent:working and is not a stale
claim (below), end the run with "busy: ". Post nothing.
- Answered: a ticket labeled
agent:needs-infooragent:needs-customerwith a human reply newer than your last question. Look at its Linear comments and at its Slack thread (the link attached to the ticket). - Reviewed: a ticket labeled
agent:pr-openwhose PR has a review thread or a red check left without your answer for an hour, or is still a draft with CI green. The session that built it did not wake. Address it asbuild-ticketautonomous mode says, then label itagent:pr-openagain. - Asked for: a ticket labeled
agent:go, or a message inHOOP_AGENT_SLACK_CHANNELthat names a ticket ID and does not start with 🤖. Addagent:goto that ticket. - New: label
Support, statusTodo, no assignee, noagent:*label. Oldest first.
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 · 170 lines · 62 tokens per session scan A 7c6b529bff57
support-agent is a skill published in the GitHub repository hoophq/hoop (837 stars, last pushed today), licensed MIT. It adds 62 tokens to every session and 1,918 once invoked, about $0.0002 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-10-24.
Other skills, from other repositories
stale-sweep
Sweep the googleapis/mcp-toolbox repo for issues and PRs with no real activity in N days (default 60), sort each by whose silence it is (the author's, ours, or nobody's), and draft the nudge or close comment. Use whenever a maintainer asks for a stale sweep, backlog cleanup, or an SLO check, e.g. "stale sweep", "find…
linear-tickets
Create or update high-quality Linear tickets while preserving the originating report, diagnostic links, attachments, and reporter/requester attribution. Read this whenever someone asks to create, recreate, or update a Linear issue.
imaging-data-commons
Query and download public cancer imaging data from NCI Imaging Data Commons using idc-index. Use for accessing large-scale radiology (CT, MR, PET) and pathology datasets for AI training or research. No authentication required. Query by metadata, visualize in browser, check licenses.
geo-database
Access NCBI GEO for gene expression/genomics data. Search/download microarray and RNA-seq datasets (GSE, GSM, GPL), retrieve SOFT/Matrix files, for transcriptomics and expression analysis.
brenda-database
Access BRENDA enzyme database via SOAP API. Retrieve kinetic parameters (Km, kcat), reaction equations, organism data, and substrate-specific enzyme information for biochemical research and metabolic pathway analysis.
clinpgx-database
Access ClinPGx pharmacogenomics data (successor to PharmGKB). Query gene-drug interactions, CPIC guidelines, allele functions, for precision medicine and genotype-guided dosing decisions.