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 thousandeyes/thousandeyes-ai-agents-toolkit --skill thousandeyes-synthetic-monitoringgit clone --depth 1 https://github.com/thousandeyes/thousandeyes-ai-agents-toolkitWrote 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/thousandeyes/thousandeyes-ai-agents-toolkit/thousandeyes-synthetic-monitoring)<a href="https://agentmods.dev/skills/thousandeyes/thousandeyes-ai-agents-toolkit/thousandeyes-synthetic-monitoring"><img src="https://agentmods.dev/badge/skills/thousandeyes/thousandeyes-ai-agents-toolkit/thousandeyes-synthetic-monitoring/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/thousandeyes/thousandeyes-ai-agents-toolkit/thousandeyes-synthetic-monitoring"><img src="https://agentmods.dev/badge/skills/thousandeyes/thousandeyes-ai-agents-toolkit/thousandeyes-synthetic-monitoring.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.00063 | $0.02058 |
| Opus 5 | $0.00032 | $0.01029 |
| Sonnet 5 | $0.00013 | $0.00412 |
| Haiku 4.5 | $0.00006 | $0.00206 |
Grade A, and why
thousandeyes-synthetic-monitoring 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.
How it starts
The opening of the file, as written. The whole thing — 152 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ThousandEyes Synthetic Monitoring
Use this skill to manage ThousandEyes synthetic monitoring through the available MCP tools. Treat synthetic monitoring as the umbrella workflow for creating, validating, updating, and deleting synthetic tests, and for deploying template-based monitoring for an application.
Use This Skill When
- A user wants to list or inspect existing ThousandEyes synthetic tests
- A user wants to create or update synthetic monitoring for an application or service
- A user wants to delete one or more synthetic tests
- A user wants to run a dynamic or ad hoc check before creating scheduled monitoring
- A user wants to deploy a template-based monitoring configuration for an application
- A user needs help deciding between Network and Application Synthetics and Browser Synthetics
Required Behavior
- Inspect the relevant ThousandEyes tool schema before using unfamiliar synthetic-monitoring tools.
- Confirm the user intent first:
list,get,create,update,delete,instant-test, ordeploy-template. - Treat
create_synthetic_test,update_synthetic_test,delete_synthetic_test, anddeploy_templateas external write actions. Get explicit user confirmation before calling them. - Treat instant-test tools as execution actions for dynamic validation. Confirm before running them unless the user explicitly asked to run the check now.
- Use read-only discovery tools without extra confirmation when they help identify the right synthetic test, agent set, or application template.
- For
updateanddelete, require bothtest_idandtest_type. - Do not invent tool arguments that are not exposed by the MCP tool schema.
- When the user gives only a test name, use discovery tools to recover the exact
test_idandtest_typebefore any write. - Map the request to the correct product language first:
- Network and Application Synthetics for network, API, DNS, and HTTP server-style monitoring
- Browser Synthetics for page-load and transaction-style browser monitoring
- Synthetic tests and templates for application monitoring workflows
- Summarize the exact payload or execution plan before running any write or instant action, then summarize the result after execution.
What ships with it
3 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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 · 152 lines · 63 tokens per session scan A 7decbe99760c
thousandeyes-synthetic-monitoring is a skill published in the GitHub repository thousandeyes/thousandeyes-ai-agents-toolkit (3 stars, last pushed 3mo ago), licensed Apache-2.0. It adds 63 tokens to every session and 2,058 once invoked, about $0.0003 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
add-community-extension
Add a community extension to the Spec Kit catalog from a GitHub issue submission. USE FOR: processing extension submission issues, validating catalog entries, updating catalog.community.json and docs/community/extensions.md, creating PRs. DO NOT USE FOR: creating new extensions from scratch, or first-party extension…
openspec-explore
Enter explore mode - a thinking partner for exploring ideas, investigating problems, and clarifying requirements. Use when the user wants to think through something before or during a change.
openspec-apply-change
Implement tasks from an OpenSpec change. Use when the user wants to start implementing, continue implementation, or work through tasks.
openspec-verify-change
Verify implementation matches change artifacts. Use when the user wants to validate that implementation is complete, correct, and coherent before archiving.
openspec-update-change
Update an OpenSpec change by revising its existing planning artifacts and keeping them coherent with one another. Use when the user wants to revise a change's plan, fold new decisions into it, or reconcile its artifacts after an edit. Never edits code.
openspec-new-change
Start a new OpenSpec change using the experimental artifact workflow. Use when the user wants to create a new feature, fix, or modification with a structured step-by-step approach.