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/echovic/boss-skill/monitoring-alertingnpx skills add echoVic/boss-skill --skill monitoring-alertinggit clone --depth 1 https://github.com/echoVic/boss-skillWrote 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/echovic/boss-skill/monitoring-alerting)<a href="https://agentmods.dev/skills/echovic/boss-skill/monitoring-alerting"><img src="https://agentmods.dev/badge/skills/echovic/boss-skill/monitoring-alerting.svg" alt="Measured on agentmods" 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 | $0.00018 | $0.00326 |
| Opus 5 | $0.00009 | $0.00163 |
| Sonnet 5 | $0.00004 | $0.00065 |
| Haiku 4.5 | $0.00002 | $0.00033 |
Grade A, and why
devops/monitoring-alerting 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 4d 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
监控告警
监控指标
| 类型 | 指标 | 阈值 |
|---|---|---|
| 应用 | 错误率 | < 1% |
| 应用 | 响应时间 | P99 < 500ms |
| 系统 | CPU使用率 | < 80% |
| 系统 | 内存使用率 | < 85% |
| 系统 | 磁盘使用率 | < 90% |
告警规则
| 级别 | 条件 | 通知方式 |
|---|---|---|
| P0 | 服务不可用 | 电话 + 短信 + 邮件 |
| P1 | 错误率 > 5% | 短信 + 邮件 |
| P2 | 响应时间 > 1s | 邮件 |
| P3 | 资源使用率 > 80% | 邮件 |
日志管理
- 集中式日志收集
- 日志分级（ERROR, WARN, INFO, DEBUG）
- 日志保留策略（30天）
- 敏感信息脱敏
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.
- 4d ago First seen · 42 lines · 18 tokens per session scan A 08afc69eaaf2
devops/monitoring-alerting is a skill published in the GitHub repository echoVic/boss-skill (553 stars, last pushed 4d ago), licensed MIT. It adds 18 tokens to every session and 326 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-08-30.
Other skills, from other repositories
large-workspace-handling
To partition large workspaces (100+ files) into scoped subagent tasks when context is insufficient.
example-skill
Example skill template used for the CreateHub template. You should never use this skill directly as it is just a template made to be updated.
bmad-github-story-dev
Set up a git worktree/branch (or reuse the current one) and run BMAD dev-story end-to-end: auto-commits per task, PR creation, label updates. Use when the user invokes the SD menu code in bmad help, or asks to start implementing the next ready story, or asks to begin dev on a story.
bmad-github-story-sync
Reconcile GitHub state with BMAD files — detect merged PRs, mark stories done in sprint-status.yaml and story files, sync GitHub labels, and clean up worktrees and branches. Use when the user invokes the SS menu code in bmad help, or asks to sync BMAD with GitHub, or just merged a PR and wants BMAD updated.
bmad-github-story-create
Sync GitHub state then plan the next story end-to-end via the BMAD create-story flow. Detects blocking dependencies via GitHub labels and updates the GitHub issue label to ready. Use when the user invokes the SC menu code in bmad help, or asks to plan/create the next story, or asks to start the next BMAD story.
bmad-github-story-review
Run BMAD adversarial code review on the current story branch and push fixes. Does NOT mark the story done — the user merges the PR on GitHub. Use when the user invokes the SR menu code in bmad help, or asks to code-review the current story, or asks for an adversarial review of the open story PR.