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 event4u-app/agent-config --skill mcpgit clone --depth 1 https://github.com/event4u-app/agent-configWrote 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/event4u-app/agent-config/mcp)<a href="https://agentmods.dev/skills/event4u-app/agent-config/mcp"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/mcp/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/event4u-app/agent-config/mcp"><img src="https://agentmods.dev/badge/skills/event4u-app/agent-config/mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00028 | $0.02241 |
| Opus 5 | $0.00014 | $0.01120 |
| Sonnet 5 | $0.00006 | $0.00448 |
| Haiku 4.5 | $0.00003 | $0.00224 |
Grade A, and why
mcp 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 8d 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 — 223 lines — stays where its author put it; the contents beside it link to each section on GitHub.
MCP Skill
When to use
Use this skill when:
- Deciding which MCP tool to use for a task
- Combining multiple MCP tools in a workflow
- Troubleshooting MCP tool errors or unexpected results
- Building commands or skills that reference MCP tools
Procedure: Use MCP tools
- Inspect available MCP servers — List configured servers (Sentry, Jira, GitHub, Playwright, Context7, Sequential Thinking) and confirm credentials/permissions for the task.
- Pick the right tool per task — Match user intent to the server table below; prefer the most specific tool over generic search.
- Chain tools when needed — Apply the Combining tools in workflows patterns; capture intermediate IDs (org slug, project slug, ticket key) before deeper calls.
- Verify and handle errors — Apply Error handling and Permission boundaries; confirm the result answers the original question before moving on.
Sentry (augment-partner-remote-mcp-sentry)
Error tracking and performance monitoring.
| Tool | Purpose | When to use |
|---|---|---|
find_organizations |
Find org slug | First call — needed for all other Sentry tools |
find_projects |
Find project slug | When filtering by project |
find_teams |
Find team slug/ID | Team-based queries |
find_releases |
Recent releases | Check deploy timing, release versions |
get_issue_details |
Full issue: stacktrace, tags | Investigating a specific error |
get_issue_tag_values |
Distribution by tag | Analyzing who/what is affected |
get_trace_details |
Trace overview | Performance investigation |
get_event_attachment |
Download attachments | Screenshots, logs on events |
search_issues |
List issues by criteria | "Show me unresolved errors" |
search_events |
Count/aggregate events | "How many errors today?" |
search_issue_events |
Filter events in an issue | "Events from last hour" |
analyze_issue_with_seer |
AI root cause analysis | When stacktrace alone isn't enough |
Key pattern: Always get org slug first → then use other tools.
See: sentry-integration skill for investigation workflow.
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.
- 8d ago First seen · 223 lines · 28 tokens per session scan A 9afb1354661e
mcp is a skill published in the GitHub repository event4u-app/agent-config (10 stars, last pushed today), licensed MIT. It adds 28 tokens to every session and 2,241 once invoked, about $0.0001 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-09-04.
Other skills, from other repositories
save-progress
Save current project task progress to local task state file for cross-session continuity. Use when the user asks to save progress, uses an equivalent localized trigger phrase, the session is interrupted, or the user wants to resume work later. Writes to .claude/project-task-state.json so next session can load it via…
meta-theory
MetaKim executable governance dispatcher. It classifies the run, loads only needed references, preserves foundational capabilities and runtime-native abilities, routes owner + weapon + dependency + runtime + OS + verification, and closes only with evidence, intent acceptance, and writeback decision.
same-set-reusable-flow-for-project-file-inventor
Reusable MetaKim file inventory classification flow. It helps separate durable sources, generated evidence, runtime mirrors, temporary state, and risky unknowns before cleanup or commit.
starreel-drama-production
Operating skill for any AI agent driving the StarReel short-drama production pipeline (script → rewrite → extract → portraits + sheets → storyboards → frames → video → voiceover → final cut) over MCP or REST. Covers the ordered workflow, the entry-point decision table (which channel each kind of customer material…
seedance-20
Generate and direct cinematic AI videos with Seedance 2.0 (ByteDance/Dreamina/Jimeng). Covers text-to-video, image-to-video, video-to-video, and reference-to-video workflows with @Tag asset references, multi-character scenes, audio design, and post-processing. Use when making AI video, writing Seedance prompts…
monorepo-management
Master monorepo management with Turborepo, Nx, and pnpm workspaces to build efficient, scalable multi-package repositories with optimized builds and dependency management. Use when setting up monorepos, optimizing builds, or managing shared dependencies.