A workspace command for attaching a pull request or Jira ticket to the current coding workspace. A pull request is a proposed code change, while Jira is a tool for tracking work items and bugs.

Use it when starting work linked to a GitHub pull request or Jira issue, such as reviewing a change or implementing a tracked task.

It keeps the relevant work reference connected to the code workspace instead of requiring developers to look up repository and ticket details manually.

ref — Command by mdsakalu

Install

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.

agentmods

npx agentmods add commands/mdsakalu/agent-plugins/ref

Clone the repo

git clone --depth 1 https://github.com/mdsakalu/agent-plugins

Per session 13 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 727 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

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	$0.00013	$0.00727
Opus 5	$0.00006	$0.00364
Sonnet 5	$0.00003	$0.00145
Haiku 4.5	$0.00001	$0.00073

Measured yesterday against content hash ff5c60f9b658, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

ref 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 yesterday.

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.

workspace/commands/ref.md · 53 lines

How it starts

The opening of the file, as written. The whole thing — 53 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Add a reference (PR, Jira ticket) to the current workspace.

Resolve the metarepo path by reading ~/.claude/workspace-config.json and expanding ~ to $HOME.

The user's request: $ARGUMENTS

Steps

Read ~/.claude/workspace-config.json to get the metarepo path. Expand ~ to $HOME.
Determine the current workspace:
- Infer from cwd: match */repos/<repo>/<workspace>* to extract repo and workspace
- Or use .workspace.json symlink if it exists in cwd
- If unable to determine, ask the user
Read <metarepo>/notes/<repo>/<workspace>/workspace.json (or via .workspace.json symlink).
Read <metarepo>/repos/<repo>/.repo.json for GitHub owner/repo info.
Parse the user's input for the reference:
- PR: #1234, 1234, PR #1234, or a full GitHub PR URL
- Jira ticket: PROJ-1234, TEAM-123, WORK-456 (uppercase project key + dash + number)
For PR references:
- Resolve full URL using .repo.json: https://github.com/<owner>/<repo>/pull/<number>
- Get PR title: gh pr view <number> --json title -q '.title' --repo <owner>/<repo>
- Capture JJ change ID: jj log -r @ --no-graph -T change_id (from workspace directory)
- Capture branch: jj log -r @ --no-graph -T 'bookmarks'
- Check for duplicates in workspace.json references
- Append to references array using jq:
```
jq --arg url "$URL" --argjson num $NUMBER --arg change_id "$CHANGE_ID" --arg branch "$BRANCH" --arg added "$(date +%Y-%m-%d)" \
  '.references += [{"type":"pr","number":$num,"url":$url,"jj_change_id":$change_id,"branch":$branch,"added":$added}]' \
  workspace.json > tmp && mv tmp workspace.json
```

For Jira references:

Check for duplicates

Append using jq:

jq --arg key "$KEY" --arg added "$(date +%Y-%m-%d)" \
  '.references += [{"type":"jira","key":$key,"added":$added}]' \
  workspace.json > tmp && mv tmp workspace.json

Confirm what was added and show the updated references.

Read the full file on GitHub · 53 lines

Changes

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.

yesterday First seen · 53 lines · 13 tokens per session scan A ff5c60f9b658

Subscribe to this mod's changes

ref is a command published in the GitHub repository mdsakalu/agent-plugins (4 stars, last pushed 2mo ago), licensed MIT. It adds 13 tokens to every session and 727 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-31.

Code review Debugging Planning

ref

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

Steps

What this file has done since we first saw it

Other commands, from other repositories

checklist

clarify

specify

analyze

converge

implement