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-issue-triagegit 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-issue-triage)<a href="https://agentmods.dev/skills/ayushcodes10/echo-mem/source-command-github-issue-triage"><img src="https://agentmods.dev/badge/skills/ayushcodes10/echo-mem/source-command-github-issue-triage/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-issue-triage"><img src="https://agentmods.dev/badge/skills/ayushcodes10/echo-mem/source-command-github-issue-triage.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.00022 | $0.00224 |
| Opus 5.5 | $0.00009 | $0.00090 |
| Sonnet 5.5 | $0.00004 | $0.00045 |
| Haiku 4.5 | $0.00002 | $0.00022 |
Grade A, and why
source-command-github-issue-triage 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-issue-triage
Use this skill when the user asks to run the migrated source command github-issue-triage.
Command Template
issue-triage
Intelligent issue classification and triage.
Usage
npx Codex-flow github issue-triage [options]
Options
--repository <owner/repo>- Target repository--auto-label- Automatically apply labels--assign- Auto-assign to team members
Examples
# Triage issues
npx Codex-flow github issue-triage --repository myorg/myrepo
# With auto-labeling
npx Codex-flow github issue-triage --repository myorg/myrepo --auto-label
# Full automation
npx Codex-flow github issue-triage --repository myorg/myrepo --auto-label --assign
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 · 22 tokens per session scan A 888121e26290
source-command-github-issue-triage is a skill published in the GitHub repository ayushcodes10/echo-mem (2 stars, last pushed 1mo ago), licensed Apache-2.0. It adds 22 tokens to every session and 224 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
github-ops
GitHub CLI for issues, PRs, code search, CI logs, releases, and API queries. Requires gh CLI and auth.
syncing-memory-filesystem
Diagnose and repair MemFS repository setup, remote sync, authentication failures, optional backup remotes, or merge/rebase conflicts. Do not load for routine memory reads or edits.
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.
init
Turn on Rekal memory in the current repository by running rekal init. Use when the user asks to initialize or set up Rekal here, or when a rekal command reported the repository is not initialized. Once per repository. Do not offer this merely because a repo lacks a .rekal/ store — most repos do not want one.
board-pilot
Board-driven implementation pipeline: polls a GitHub Project, arms an item when dragged into the trigger column, advances it stage by stage to a human-gated draft PR. Stages configured per project in workflow/projects/ .yaml. Trigger: "/board-pilot", "board pilot", "auto-implement from board", "pipeline runner".
sweep-now
Run the three read-mostly vault sweeps for stale tracker items, dormant-note candidates, and broken wikilinks, then append one dated result to SWEEPLOG.md.