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/russeell/jobfindsmeWrote 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/russeell/jobfindsme/jobfindsme)<a href="https://agentmods.dev/mcp/russeell/jobfindsme/jobfindsme"><img src="https://agentmods.dev/badge/mcp/russeell/jobfindsme/jobfindsme/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/russeell/jobfindsme/jobfindsme"><img src="https://agentmods.dev/badge/mcp/russeell/jobfindsme/jobfindsme.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
jobfindsme 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.
What it actually says
{
"jobfindsme": {
"command": "bash",
"args": [
"-lc",
"exec \"${JOBFINDSME_PYTHON:-$HOME/.jobfindsme/runtime/bin/python}\" -m jobfindsme.mcp"
]
}
}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 · 9 lines scan A 806b892e85cf
jobfindsme is an MCP server published in the GitHub repository russeell/jobfindsme (15 stars, last pushed 19d 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-30.
Other mcp servers, from other repositories
meetey
MCP server "meetey" as configured in jej2k5/meetey. Runs locally from the meetey npm package.
rag-rat
CLI and MCP entrypoint for indexing repositories into local source, graph, history, and memory evidence. Runs locally from the @rag-rat/bin npm package.
plonk
MCP server for Plonk: macOS window zones, workspaces, keep-awake, screenshots and on-device OCR. Runs locally from the plonk-mcp npm package.
obsidian-everywhere
Graph context, semantic search, guarded edits, and reviewable Git for local Obsidian vaults. Runs locally from the obsidian-everywhere npm package.
unified-ai-system
MCP server "unified-ai-system" as configured in happy520ai/unified-ai-system. Runs in Docker (ghcr.io/happy520ai/unified-ai-system/mcp-server:0.6.0).
raycast
Raycast workflow automation MCP server with 9 tools. Runs locally from the raycast-mcp-server npm package.