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 helloaigent-dev/helloaigent-subscriber --skill hello-aigentgit clone --depth 1 https://github.com/helloaigent-dev/helloaigent-subscriberWrote 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/helloaigent-dev/helloaigent-subscriber/hello-aigent)<a href="https://agentmods.dev/skills/helloaigent-dev/helloaigent-subscriber/hello-aigent"><img src="https://agentmods.dev/badge/skills/helloaigent-dev/helloaigent-subscriber/hello-aigent/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/helloaigent-dev/helloaigent-subscriber/hello-aigent"><img src="https://agentmods.dev/badge/skills/helloaigent-dev/helloaigent-subscriber/hello-aigent.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.00104 | $0.01183 |
| Opus 5.5 | $0.00042 | $0.00473 |
| Sonnet 5.5 | $0.00021 | $0.00237 |
| Haiku 4.5 | $0.00010 | $0.00118 |
Grade A, and why
hello-aigent 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.
How it starts
The opening of the file, as written. The whole thing — 91 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Hello Aigent subscriber
Hello Aigent is an opt-in subscribe layer for AI agents (RSS-for-agents). A website can publish a signed feed. An agent may subscribe, fetch new updates, verify the Ed25519 signature, and only then act.
This plugin talks to the existing Hello Aigent subscriber MCP (@helloaigent-dev/subscriber). There is no API key. Subscriptions, tokens, and policy live locally under ~/.hello-aigent/ (never show stored tokens).
Many people using this plugin are not developers. Speak plainly. Confirm what you are about to do before you subscribe.
When to use this skill
- The user asks to subscribe their agent to a site or to Hello Aigent.
- The user asks whether a website has a Hello Aigent feed.
- The user wants new updates, a digest, or to stop following a feed.
- You are about to use any
hello_aigent_*tool.
Consent first (required)
Subscribe only with the principal's consent — the person (or account) this agent acts for.
- If they said to subscribe to a named site or feed, that is consent for that feed.
- If you merely found a feed while visiting a site, tell them and ask before calling
hello_aigent_subscribe. - Do not silently auto-subscribe in chat just because a site has a feed.
hello_aigent_check_sitemay subscribe on its own when local policy isauto_subscribe: on. Preferhello_aigent_check_siteonly to detect a feed, then subscribe explicitly after they agree — or ask them to set policy if they want automatic subscribe-on-visit. - Unsubscribe is always allowed and is one call. Offer it if they change their mind.
The default principal is a local user@host identity until they set a stable one (often an email) in ~/.hello-aigent/policy.json.
How to find a feed
Publishers advertise discovery at:
https://<site>/.well-known/hello-aigent.json
Example (live dogfood feed): https://helloaigent.dev → https://helloaigent.dev/.well-known/hello-aigent.json
If the user names a website, check that discovery URL (or pass any page URL on the site to hello_aigent_check_site). If there is no discovery file and no rel="agent-feed" link, say the site does not publish a Hello Aigent feed yet.
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 First seen · 91 lines · 104 tokens per session scan A 05532983262a
hello-aigent is a skill published in the GitHub repository helloaigent-dev/helloaigent-subscriber (0 stars, last pushed 1mo ago), licensed MIT. It adds 104 tokens to every session and 1,183 once invoked, about $0.0004 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…
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…