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/htlin222/hahow-mentor-agentWrote 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/htlin222/hahow-mentor-agent/hahow-watcher)<a href="https://agentmods.dev/mcp/htlin222/hahow-mentor-agent/hahow-watcher"><img src="https://agentmods.dev/badge/mcp/htlin222/hahow-mentor-agent/hahow-watcher/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/htlin222/hahow-mentor-agent/hahow-watcher"><img src="https://agentmods.dev/badge/mcp/htlin222/hahow-mentor-agent/hahow-watcher.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
hahow-watcher 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 10d 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
{
"hahow-watcher": {
"command": "bun",
"args": [
"./channels/hahow-watcher/hahow-watcher.ts"
],
"env": {
"HAHOW_PROJECT": "${PWD}",
"HAHOW_POLL_MINUTES": "60"
}
}
}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.
- 10d ago First seen · 12 lines scan A 72811e8966b7
hahow-watcher is an MCP server published in the GitHub repository htlin222/hahow-mentor-agent (1 stars, last pushed 3mo 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
context7
Gives the agent up-to-date documentation and code examples for libraries and frameworks, fetched on demand so answers are not stuck at the model's training cutoff. Runs locally from the @upstash/context7-mcp npm package.
microsoft-learn
MCP server "microsoft-learn", hosted remotely at learn.microsoft.com, as configured in tractorjuice/arckit-codex.
stepik-mcp
MCP server "stepik-mcp" as configured in seniorcat/stepik-mcp. Runs locally from the stepik-mcp Python package.
reading-companion
MCP server "reading-companion" as configured in aby0/reading-companion. Runs locally from the reading-companion Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.
component-explorer
MCP server "component-explorer" as configured in microsoft/vscode. Launched with npm exec --no -- component-explorer mcp -p ./test/componentFixtures/component-ex.