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 ayushcodes10/echo-mem --skill source-command-github-code-reviewgit clone --depth 1 https://github.com/ayushcodes10/echo-memWrote 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/ayushcodes10/echo-mem/source-command-github-code-review)<a href="https://agentmods.dev/skills/ayushcodes10/echo-mem/source-command-github-code-review"><img src="https://agentmods.dev/badge/skills/ayushcodes10/echo-mem/source-command-github-code-review/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/ayushcodes10/echo-mem/source-command-github-code-review"><img src="https://agentmods.dev/badge/skills/ayushcodes10/echo-mem/source-command-github-code-review.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.00016 | $0.00202 |
| Opus 5.5 | $0.00006 | $0.00081 |
| Sonnet 5.5 | $0.00003 | $0.00040 |
| Haiku 4.5 | $0.00002 | $0.00020 |
Grade A, and why
source-command-github-code-review 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 1mo 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
source-command-github-code-review
Use this skill when the user asks to run the migrated source command github-code-review.
Command Template
code-review
Automated code review with swarm intelligence.
Usage
npx Codex-flow github code-review [options]
Options
--pr-number <n>- Pull request to review--focus <areas>- Review focus (security, performance, style)--suggest-fixes- Suggest code fixes
Examples
# Review PR
npx Codex-flow github code-review --pr-number 456
# Security focus
npx Codex-flow github code-review --pr-number 456 --focus security
# With fix suggestions
npx Codex-flow github code-review --pr-number 456 --suggest-fixes
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.
- 1mo ago First seen · 37 lines · 16 tokens per session scan A a69aeace6ef8
source-command-github-code-review is a skill published in the GitHub repository ayushcodes10/echo-mem (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 16 tokens to every session and 202 once invoked, about $0.0001 per session on Opus 5.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-09-12.
Other skills, from other repositories
pre-pr
Prepare a Honcho change for a pull request to plastic-labs/honcho. Invoke before opening a PR, when drafting a PR body, when asked if a branch is PR-ready, or when filling the pull request template. Checks the linked issue, required tests and docs, then writes Description / Proofs / Fixes.
end
Close a work session — log what happened, update state and the decision log, propose durable memory updates, and check for uncommitted or unpushed work.
commit-history
List recent git commits linked to agent sessions, optionally filtered by branch or repo. Use when the user asks "show agent commits", "what has the agent shipped", "list linked commits", or wants commits with their session context.
github-pr-workflow
Prepare a GitHub pull request from a feature branch — branch hygiene, commit shape, title/body, verification notes, screenshots for UI work, and replies to review comments.
memory-to-skill
Turn workflows from your MemSearch memory into reusable skills. Use when the user asks to make/create/extract/distill a skill from what they just did or from past work, review skill candidates, install a distilled skill, or 'turn this into a skill'. Manages MemSearch procedural-memory candidates under…
git-pr-workflows-git-workflow
Guide changes through code checks, testing, commits, and pull request preparation. Use when coordinating a complete Git workflow and verifying readiness for collaboration.