Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/jackchuka/ghpmnpx agentmods add skills/jackchuka/ghpm/ghpm-viewWrote 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/jackchuka/ghpm/ghpm-view)<a href="https://agentmods.dev/skills/jackchuka/ghpm/ghpm-view"><img src="https://agentmods.dev/badge/skills/jackchuka/ghpm/ghpm-view/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/jackchuka/ghpm/ghpm-view"><img src="https://agentmods.dev/badge/skills/jackchuka/ghpm/ghpm-view.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.00029 | $0.01229 |
| Opus 5.5 | $0.00012 | $0.00492 |
| Sonnet 5.5 | $0.00006 | $0.00246 |
| Haiku 4.5 | $0.00003 | $0.00123 |
Grade A, and why
ghpm-view 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.
How it starts
The opening of the file, as written. The whole thing — 128 lines — stays where its author put it; the contents beside it link to each section on GitHub.
ghpm-view
PREREQUISITE: Read
../ghpm-shared/SKILL.mdfor prerequisites and error handling.
Drill into a specific named view or run an ad-hoc filter against project items.
Arguments
/ghpm-view— with no args, list available views (same as the Views section of/ghpm-status)/ghpm-view <view name>— fuzzy match against view names in config/ghpm-view <free-form filter>— natural language filter against field values/ghpm-view --refresh— force re-fetch cache before querying
Workflow
Phase 1: Load Config and Cache
Follow the startup sequence in ../ghpm-shared/SKILL.md and load cache per ../ghpm-shared/references/cache.md. If --refresh flag is present, skip cache and re-fetch.
Phase 2: Resolve Query
-
If no arguments: list available views with item counts and stop.
-
If arguments provided, try to match against view names first:
- Normalize input (lowercase, strip punctuation).
- Compare against view names from config (also normalized).
- Use substring matching: "standup" matches "daily standup", "triage" matches "Task Triage", "appshell" matches "AppShell".
- If exactly one view matches: use that view's filter and layout.
- If multiple views match: show matches and ask user to pick.
-
If no view matches, treat input as ad-hoc filter:
- Match user's words against known field option names from
.ghpm/config.json. - Match
@usernameagainst assignee fields. - Match workflow column names (e.g., "in progress" -> InProgress).
- Build a filter from matched fields.
- Match user's words against known field option names from
Phase 3: Apply Filter
-
Filter cached items based on the resolved query. Apply filter syntax per
../ghpm-shared/references/filter.md. -
Apply sort if the view has sort fields: sort items by the specified fields and directions.
Phase 4: Format Output
- Format based on layout type, following conventions in
../ghpm-shared/references/format.md:
Board layout — group items by workflow column as vertical lists:
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 · 128 lines · 29 tokens per session scan A 5e686aa4c999
ghpm-view is a skill published in the GitHub repository jackchuka/ghpm (20 stars, last pushed 11d ago), licensed MIT. It adds 29 tokens to every session and 1,229 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-08-30.
Other skills, from other repositories
git-issue-create
Open one standalone GitHub issue with gh - duplicate-checked first, conventional title, repo-template-aware body, auto-resolved labels. Use for every issue-filing request however casual: "open an issue", "file a bug", "make a ticket", "/git-issue-create", "track this", "note this down", "we should fix X later", or…
git-issue-triage
Groom an open GitHub backlog with gh - one read-only sweep, every open issue bucketed into exactly one category (unlabeled, unprioritized, stale, likely duplicate, closeable, blocked, healthy), a per-issue report, per-category confirmation, then batched label / state / comment edits. Use when the user says "triage…
git-issue-start
Take a GitHub issue from open to a checked-out branch - assign it to you, mark it in progress if the repo has such a label, derive a conventional branch name from its type: label, branch off the detected base. Use for "start issue 42", "work on #42", "/git-issue-start 42", "let's do 42", "pick up that issue", "take…
airtable-automation
Automate Airtable tasks via Rube MCP (Composio): records, bases, tables, fields, views. Always search tools first for current schemas.
360-feedback-system
360 feedback register: reviewer, subject, review cycle, visibility, due date and score, as CSV, SQL, JSON Schema or Notion on request. Use for 360 reviews or peer feedback cycles.
alumni-re-hire-tracker
Alumni and re-hire register: former role, last working day, re-hire eligibility, current employer and re-engagement date, as CSV, SQL, JSON Schema or Notion on request. Use for alumni outreach.