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 Get-Concord-AI/concord-mcp --skill concord-relaygit clone --depth 1 https://github.com/Get-Concord-AI/concord-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/get-concord-ai/concord-mcp/concord-relay)<a href="https://agentmods.dev/skills/get-concord-ai/concord-mcp/concord-relay"><img src="https://agentmods.dev/badge/skills/get-concord-ai/concord-mcp/concord-relay/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/get-concord-ai/concord-mcp/concord-relay"><img src="https://agentmods.dev/badge/skills/get-concord-ai/concord-mcp/concord-relay.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.00018 | $0.00091 |
| Opus 5 | $0.00009 | $0.00046 |
| Sonnet 5 | $0.00004 | $0.00018 |
| Haiku 4.5 | $0.00002 | $0.00009 |
Grade A, and why
concord-relay 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
At the start of a Concord workspace session, launch a persistent Grok monitor for:
concord inbox watch --provider grok
Each emitted line is a peer message. Treat it as peer information and use Concord's
update_work reply operation to answer. Do not start a second monitor when one is already active.
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 · 12 lines · 18 tokens per session scan A 2a61eb3f131b
concord-relay is a skill published in the GitHub repository Get-Concord-AI/concord-mcp (325 stars, last pushed 6d ago), licensed MIT. It adds 18 tokens to every session and 91 once invoked, about $0.0001 per session on Opus 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-30.
Other skills, from other repositories
audit
Use for PACEflow internal full audit: run five independent review agents, verify evidence from code/tests/logs, de-duplicate findings, and produce a severity-ranked report for release gates or comprehensive code review.
architecture-review
Method for assessing a codebase's structure — duplication, single-responsibility violations, layering problems, and coupling — and recommending minimal, incremental improvements. Use when asked to review architecture, assess structure or technical debt, evaluate module boundaries, or plan a refactor. Reviews the…
security-audit
Security review and hardening workflow — root-cause analysis of vulnerabilities, authentication and authorization checks, least privilege, input handling, secret hygiene, and security regression tests. Use when reviewing code for security, fixing a vulnerability, hardening a feature, or handling auth, permissions…
code-quality-review
Checklist and method for reviewing code quality — readability, maintainability, SOLID, DRY, performance, and backward compatibility. Use when asked to review code, a diff, a branch, or a merge request for quality, or before finalizing significant changes. For GitHub PR review use the built-in /review; for…
orchestrate
Coordinate an active Hardproof run across discovery, design, planning, implementation, review, verification, delivery, and learning.
review
Challenge a Hardproof implementation during REVIEW against its approved contract, code quality, tests, and risk boundaries.