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 Telemark-Digital/apify-monitoring-workflows --skill bluesky-keyword-alertsgit clone --depth 1 https://github.com/Telemark-Digital/apify-monitoring-workflowsWrote 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/telemark-digital/apify-monitoring-workflows/bluesky-keyword-alerts)<a href="https://agentmods.dev/skills/telemark-digital/apify-monitoring-workflows/bluesky-keyword-alerts"><img src="https://agentmods.dev/badge/skills/telemark-digital/apify-monitoring-workflows/bluesky-keyword-alerts/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/telemark-digital/apify-monitoring-workflows/bluesky-keyword-alerts"><img src="https://agentmods.dev/badge/skills/telemark-digital/apify-monitoring-workflows/bluesky-keyword-alerts.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.00031 | $0.00475 |
| Opus 5 | $0.00015 | $0.00237 |
| Sonnet 5 | $0.00006 | $0.00095 |
| Haiku 4.5 | $0.00003 | $0.00047 |
Grade A, and why
bluesky-keyword-alerts 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.
What it actually says
Bluesky Keyword Alerts
Use this skill for bounded one-off discovery of public Bluesky posts through the Apify Actor uplifted_novice_vbl/bluesky-keyword-mention-alerts. The Actor is independent and is not affiliated with Bluesky Social PBC.
Direct Actor Use
Before calling the MCP Actor tool, identify the search target and keep the run small. If the user has not provided a target, ask for one keyword, handle, mention, or hashtag. Apify charges can apply to Actor runs and delivered records, so default to preview-sized limits.
Recommended discovery input:
{
"keywords": ["product research"],
"handles": [],
"hashtags": [],
"excludeTerms": [],
"langs": ["en"],
"onlyNew": false,
"maxPostsPerRun": 10,
"sort": "latest",
"resetState": false
}
Use only the MCP Actor tool for uplifted_novice_vbl/bluesky-keyword-mention-alerts. Do not call unrelated Apify Actor tools or broaden the actor set. If the first response does not include enough dataset detail, use get-dataset-items only with the dataset ID from that same run and keep its limit small. Use get-actor-run or get-key-value-store-record only when needed for that same run. Never call abort-actor-run during normal discovery; abort only when the user explicitly asks to stop a run.
Monitoring Boundary
When the user asks to monitor, schedule, alert, or deliver only new posts over time, explain that this plugin does not run in the background. Tell them to create a persistent saved Apify Task with onlyNew: true, verify maxPostsPerRun <= 100, and connect the repository n8n workflow or the public Make shared scenario.
Do not place webhook URLs, tokens, private handles, customer identifiers, or secrets in examples.
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 First seen · 37 lines · 31 tokens per session scan A 16c7f9f12d46
bluesky-keyword-alerts is a skill published in the GitHub repository Telemark-Digital/apify-monitoring-workflows (1 stars, last pushed 10d ago), licensed MIT. It adds 31 tokens to every session and 475 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
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…
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…