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/apify/apify-mcp-server/bug-triagenpx skills add apify/apify-mcp-server --skill bug-triagegit clone --depth 1 https://github.com/apify/apify-mcp-serverWhat 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.00056 | $0.01685 |
| Opus 5 | $0.00028 | $0.00843 |
| Sonnet 5 | $0.00011 | $0.00337 |
| Haiku 4.5 | $0.00006 | $0.00169 |
Grade C, and why
bug-triage scanned grade C with 1 finding 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 yesterday.
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.
Recursive force deletehighDestructive command
rm -rf with a variable or a broad path is one typo away from removing the wrong tree.
4. **npx cache corruption**: Stale cache prevents stdio server from starting. Fix: `rm -rf ~/.npm/_npx` (macOS/Linux) or `rmdir /s /q %LOCALAPPDATA%\npm-cache\_npx` (Windows). How it starts
The opening of the file, as written. The whole thing — 148 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Bug Triage
Triage open bug issues on apify/apify-mcp-server. Analyze, draft responses, get approval, post.
Permissions
- Read-only by default: listing issues (
gh issue list), viewing details and comments (gh issue view) — do these automatically, no need to ask. - Write requires approval: commenting (
gh issue comment), closing (gh issue close), editing (gh issue edit) — always present the draft and wait for explicit user approval before executing.
Step 0: Parse arguments
$ARGUMENTS controls scope:
| Input | Behavior |
|---|---|
623 641 639 |
Triage specific issue numbers |
--label bug |
Triage all open issues with label (default: bug) |
--all |
Triage all open bug-labeled issues |
| (empty) | Same as --all |
Step 1: Fetch issues
Use the arguments parsed in Step 0 to determine what to fetch.
If specific issue numbers were provided, skip the list queries and fetch each issue directly:
gh issue view <number> --repo apify/apify-mcp-server --comments
Otherwise (label mode, --all, or empty), fetch open bug reports. Use the label from Step 0 (default: bug). Bug reports come in two forms — find both:
- By label: issues with the parsed label
- By title prefix: issues with
[Bug]in the title (the bug report template adds this, but the label isn't always applied)
# By label (use the label from Step 0, default: bug)
gh issue list --repo apify/apify-mcp-server --label <label> --state open --json number,title,labels,createdAt,body --limit 30
# By title prefix (catches unlabeled bug reports)
gh issue list --repo apify/apify-mcp-server --state open --search "[Bug] in:title" --json number,title,labels,createdAt,body --limit 30
Merge both lists and deduplicate by issue number.
For each issue, fetch full details including all comments (comments often contain the real context):
gh issue view <number> --repo apify/apify-mcp-server --comments
Always read comments before drafting a response. Previous team members may have already replied, asked for details, or provided workarounds. Don't duplicate existing responses.
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.
- yesterday First seen · 148 lines · 56 tokens per session scan C a020404b69ce
bug-triage is a skill published in the GitHub repository apify/apify-mcp-server (5,486 stars, last pushed 4d ago), licensed MIT. It adds 56 tokens to every session and 1,685 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it C with 1 finding (recursive force delete). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
agent-code-analyzer
Agent skill for code-analyzer - invoke with $agent-code-analyzer.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
haiku
When writing a haiku for this bot, follow these conventions.
deploy-docker-compose
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack…
azure-mgmt-botservice-dotnet
Azure Resource Manager SDK for Bot Service in .NET. Management plane operations for creating and managing Azure Bot resources, channels (Teams, DirectLine, Slack), and connection settings. Triggers: "Bot Service", "BotResource", "Azure Bot", "DirectLine channel", "Teams channel", "bot management .NET", "create bot".
dogfood
Systematically explore and test a mobile app on iOS/Android with agent-device to find bugs, UX issues, and other problems. Use when asked to dogfood, QA, exploratory test, find issues, bug hunt, or test this app on mobile.