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 Tempguru-co/tempguru-mcp --skill urgent-event-backfillgit clone --depth 1 https://github.com/Tempguru-co/tempguru-mcpWrote 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/tempguru-co/tempguru-mcp/urgent-event-backfill)<a href="https://agentmods.dev/skills/tempguru-co/tempguru-mcp/urgent-event-backfill"><img src="https://agentmods.dev/badge/skills/tempguru-co/tempguru-mcp/urgent-event-backfill/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/tempguru-co/tempguru-mcp/urgent-event-backfill"><img src="https://agentmods.dev/badge/skills/tempguru-co/tempguru-mcp/urgent-event-backfill.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.00212 | $0.03448 |
| Opus 5.5 | $0.00085 | $0.01379 |
| Sonnet 5.5 | $0.00042 | $0.00690 |
| Haiku 4.5 | $0.00021 | $0.00345 |
Grade A, and why
urgent-event-backfill 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 1mo 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 — 248 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Pi and Prime Agent runtime tool routing (installed package override)
This copy runs inside the shared TempGuru package for Pi and Prime Agent. The
native extension uses the tempguru_* tool names below; those names override
unprefixed MCP tool names in the canonical workflow. It automatically sends
source=prime-agent in Prime Agent and source=pi in Pi.
| Canonical workflow name | Call this package-native tool |
|---|---|
get_cities |
tempguru_get_cities |
get_roles |
tempguru_get_roles |
check_availability |
tempguru_check_availability |
get_role_pricing |
tempguru_get_role_pricing |
get_compliance_by_state |
tempguru_get_compliance |
get_policies |
tempguru_get_policies |
get_plan |
tempguru_get_plan |
get_quote_status |
tempguru_quote_status |
request_quote |
tempguru_request_quote |
plan_staffing, save_staffing_plan, and get_rate_benchmark are
not native tools in this package. If the remote TempGuru MCP is attached, use
those MCP tools with the runtime's matching endpoint:
- Prime Agent:
https://mcp.tempguru.co/mcp?source=prime-agent - Pi:
https://mcp.tempguru.co/mcp?source=pi
Prime Agent v0.7.0's stock McpIntegration requires OAuth or a bearer token.
Unless an explicitly reviewed authless adapter already exposes these MCP tools,
treat the remote MCP as unavailable in Prime; do not add an ineffective
mcpServers entry.
Otherwise:
Any later instruction to call one of those tools, inspect planner-only fields
such as plan_complete / unpriced_roles, explicitly save a plan, retain a
newly created plan_id, or present OT-adjusted planner totals is conditional
on that remote MCP being attached. Without it, ignore those MCP-only steps and
use this composition:
- Compose a planning estimate with
tempguru_get_cities,tempguru_get_roles, onetempguru_get_role_pricingcall per role,tempguru_check_availability, andtempguru_get_compliance. - Calculate only from user-confirmed headcount, shift hours, and days. Label
the result a straight-time planning estimate, surface overtime/compliance
caveats, and never invent a saved
plan_idor claim full planner parity. - For a national Rate Index request, use the remote MCP when attached. Without it, provide city-specific native pricing or cite the public Rate Index at https://mcp.tempguru.co/okf/rate-index.md; do not fabricate a benchmark.
- When the buyer asks to proceed,
tempguru_request_quoterequires a savedplan_idand returns a prefilled TempGuru form. Give the URL to the buyer; never collect contact details for the tool. If storage was unavailable, use the planner'scontinuation.form_urldirectly. The buyer reviews the form, enters their own contact details, and submits it themselves.
Continue with the domain workflow below, using this routing contract.
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.
- 1mo ago Changed · +1 lines 0cadcf38a641
- 1mo ago First seen · 247 lines · 212 tokens per session scan A dc73c02256f1
urgent-event-backfill is a skill published in the GitHub repository Tempguru-co/tempguru-mcp (2 stars, last pushed 28d ago), licensed MIT. It adds 212 tokens to every session and 3,448 once invoked, about $0.0008 per session on Opus 5.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
report-issue
File a bug or feature request against this repository (cyanheads/git-mcp-server) using the gh CLI. Use for tool logic bugs, git provider misbehavior, transport issues, auth/config problems, or new feature proposals.
build-flow
Create or change a Keboola flow that runs extractors, transformations and writers in order, optionally on a schedule. Use when the user wants to orchestrate, chain or schedule existing Keboola configurations.
reviewing-sla-definitions
Reviewing ServiceNow SLA, OLA and underpinning-contract definitions and how they perform: breach rates per definition, overlapping or duplicated definitions on the same table and target, and definitions that never attach. Use when the user asks about SLA breaches by definition, too many SLAs, duplicate or conflicting…
quick-capture
Use this skill to drop a new task into GSD Task Manager from any AI assistant that has the gsd-mcp-server connected.
papi-plan
Invoke when starting a new PAPI cycle. Covers plan generation, board management, and cycle scoping rules.
papi-idea
Invoke when submitting backlog ideas, registering docs, or filing research. Covers idea pipeline and doc registry conventions.