Hacker News: c5huracan

New comment by c5huracan in "Show HN: GitAgent – An open standard that turns any Git repo into an AI agent"

c5huracan — Sat, 14 Mar 2026 20:30:34 +0000

The bottleneck isn't "how do I define my agent." It's "how do agents find the right tool for their task."

I run a search service that 110+ agents use. They don't browse catalogs or read specs. They describe what they need ("MCP server for Postgres") and expect results back immediately. The definition format matters far less than whether the description is good and whether something can find it.

SKILL.md, AGENTS.md, SOUL.md, they're all converging on the same idea. That's fine. But the portability win only kicks in once there's a discovery layer that can index all of them. Without that, these files are just README.md with a new name.

New comment by c5huracan in "Show HN: Rudel – Claude Code Session Analytics"

c5huracan — Fri, 13 Mar 2026 14:17:04 +0000

The "no meaningful benchmark for good agentic session performance" point resonates. Success varies so much by task type that a single metric is almost meaningless. A 60-second documentation lookup and a 30-minute refactoring session could both be successes.

Curious what shape the benchmark takes. Are you thinking per-task-type baselines, or something more like an aggregate efficiency score?

New comment by c5huracan in "Show HN: OneCLI – Vault for AI Agents in Rust"

c5huracan — Fri, 13 Mar 2026 02:11:59 +0000

Use Vault and use a proxy. They address different problems.

Vault protects keys at rest, but the agent still gets them at runtime. The proxy keeps the key away from the agent entirely, which closes key leakage. But a prompt-injected agent can still exfiltrate data it reads through the proxy. The trust boundary shifts, it doesn't disappear.

Looks like OneCLI combines both into one tool, which is the right call.

New comment by c5huracan in "Show HN: A2Apex – Test, certify, and discover trusted A2A agents"

c5huracan — Thu, 12 Mar 2026 18:33:20 +0000

The trust scoring layer is the interesting part here. The agent ecosystem has a discovery problem and a trust problem, and most tools today only tackle discovery. Being able to evaluate reliability before you connect changes the calculus.

Curious how the trust score works in practice. Is it purely automated test results, or do you plan to incorporate usage signals over time (uptime, response quality)?

Show HN: Search 7,500 MCP servers across NPM, PyPI, and the official registry

c5huracan — Thu, 12 Mar 2026 15:21:20 +0000

Article URL: https://api.rhdxm.com/blog/crawled-7500-mcp-servers

Comments URL: https://news.ycombinator.com/item?id=47352029

Points: 3

# Comments: 0