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.
git clone --depth 1 https://github.com/Tempguru-co/tempguru-agent-skillsWrote 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/mcp/tempguru-co/tempguru-agent-skills/tempguru-event-staffing)<a href="https://agentmods.dev/mcp/tempguru-co/tempguru-agent-skills/tempguru-event-staffing"><img src="https://agentmods.dev/badge/mcp/tempguru-co/tempguru-agent-skills/tempguru-event-staffing/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/mcp/tempguru-co/tempguru-agent-skills/tempguru-event-staffing"><img src="https://agentmods.dev/badge/mcp/tempguru-co/tempguru-agent-skills/tempguru-event-staffing.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
tempguru-event-staffing 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 11d 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
{
"tempguru-event-staffing": {
"url": "https://mcp.tempguru.co/mcp",
"transport": "streamable-http"
}
}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.
- 11d ago First seen · 6 lines scan A 9caaf2a6d1d3
tempguru-event-staffing is an MCP server published in the GitHub repository Tempguru-co/tempguru-agent-skills (1 stars, last pushed 4d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. 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 mcp servers, from other repositories
tempguru-event-staffing
MCP server "tempguru-event-staffing", hosted remotely at mcp.tempguru.co, as configured in Tempguru-co/tempguru-mcp.
event-staffing
Plan W-2 event staffing from 345 catalog entries; a coordinator confirms each order. Runs locally from the tempguru-mcp npm package.
validate
Deterministic validation for AI-generated artifacts: JSON Schema, OpenAPI response, SQL syntax. Runs locally from the @machinegrade/validate npm package. Needs 2 environment variables to run.
openapi-mcp-server
A Model Context Protocol (MCP) server that exposes OpenAPI endpoints as MCP tools. Runs locally from the @lucid-spark/openapi-mcp-server npm package.
liquidus-mcp
MCP server "liquidus-mcp" as configured in aygp-dr/liquidus-005. Runs locally from the liquidus-mcp Python package.
phaedo-mcp
Carry your Phaedo cognitive fingerprint into any MCP client: style injection + decision consults. Runs locally from the phaedo-mcp npm package.