What is pick-up-issue?

A software-delivery workflow for taking a tracked issue from selection to production. It uses a separate branch and pull request, checks the change on staging, and promotes it only after live testing there.

Use it to pick up one or more backlog issues, implement each on its own branch, add tests, pass the pull-request checks, test staging, and release the approved change.

It gives issue work a repeatable path and prevents untested staging changes from reaching production. It also sets rules for priorities, decisions, configuration-only work, tests, and documentation.

How hakeemrabiuDFW/Tanda-Workforce-MCP-Server configures Claude Code

Reuse

Borrowing it

Nothing to install: this file belongs to hakeemrabiuDFW/Tanda-Workforce-MCP-Server. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/hakeemrabiuDFW/Tanda-Workforce-MCP-Server/main/.claude/skills/pick-up-issue/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/hakeemrabiuDFW/Tanda-Workforce-MCP-Server

Made for: Claude Code.

Wrote 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.

README.md

[![agentmods](https://agentmods.dev/badge/skills/hakeemrabiudfw/tanda-workforce-mcp-server/pick-up-issue/github.svg)](https://agentmods.dev/skills/hakeemrabiudfw/tanda-workforce-mcp-server/pick-up-issue)

Your own site

<a href="https://agentmods.dev/skills/hakeemrabiudfw/tanda-workforce-mcp-server/pick-up-issue"><img src="https://agentmods.dev/badge/skills/hakeemrabiudfw/tanda-workforce-mcp-server/pick-up-issue/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.

Your own site · 80×15

<a href="https://agentmods.dev/skills/hakeemrabiudfw/tanda-workforce-mcp-server/pick-up-issue"><img src="https://agentmods.dev/badge/skills/hakeemrabiudfw/tanda-workforce-mcp-server/pick-up-issue.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 62 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

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

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

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.1	$0.00062	$0.01192
Opus 5.5	$0.00025	$0.00477
Sonnet 5.5	$0.00012	$0.00238
Haiku 4.5	$0.00006	$0.00119

Measured 5d ago against content hash d5af56a86a63, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

pick-up-issue 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 5d 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.

.claude/skills/pick-up-issue/SKILL.md · 86 lines

How it starts

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

Pick up an issue

The workflow Hakeem wants every time he says "pick up an issue". One issue = one branch = one PR. Production only ever receives what passed on staging.

0. Choose and check the issue

Backlog issues carry the workforce-mcp label and a priority (P0 first, then P1, P2, P3). The ground rules and definition of done are in the tracking issue #47: read them before starting.
Do not start an issue labelled needs-decision until the decision is recorded in the issue (ask Hakeem), unless the issue states a default that can ship.
config issues (Railway variables, Tanda tokens, Tanda settings) need a person: say exactly what to change and where, and stop.
When picking up several, do them one at a time in priority order.

1. Fix

Branch from the latest origin/staging: wfm/<issue-number>-<short-slug>.
Make the smallest change that meets the issue's acceptance criteria. Follow CODING_STANDARDS.md (read-only towards Tanda, privacy filters, args.ts parsers, fail soft with warnings[]).
Add tests in tests/ for the change and its failure path. Update README / docs when users or deployers would notice.
Run all of these and fix anything red before pushing: npm run lint && npx tsc --noEmit && npm test -- --ci && npm run build

2. PR through the factory

Open a ready (non-draft) PR into staging, authored as hakeemrabiuDFW, with the body from .github/pull_request_template.md filled in (## Summary with Closes #N, ## Evidence, ## Merge Danger with **Door:** and **Blast Radius:**). The gate rejects a body missing any of them.
pr-pipeline runs checks plus the Standards and Spec Claude reviewers; pr-gate labels risk:*, posts the reviews and decides.
Fix every blocking finding and every failed check, then push again. Reply to non-blocking findings (fix, or one line on why not).
risk:low PRs are merged by the gate. risk:medium/risk:high PRs get ready-for-human. When the only remaining reason is the risk scope (checks green, no blocking findings, template complete), squash-merge it into staging: Hakeem approved this workflow. Anything else stays for him.

Read the full file on GitHub · 86 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.

5d ago First seen · 86 lines · 0 tokens per session scan A d5af56a86a63

Subscribe to this mod's changes

pick-up-issue is a skill published in the GitHub repository hakeemrabiuDFW/Tanda-Workforce-MCP-Server (2 stars, last pushed 6d ago), licensed MIT. It adds 62 tokens to every session and 1,192 once invoked, about $0.0002 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-10-24.

Commits Git and workflow Testing

github-copilot-upgrader

Use this to update the Github Copilot CLI/SDK.

microsoft/vscode · 18 tokens

workflow-patterns

Use this skill when implementing tasks according to Conductor's TDD workflow, handling phase checkpoints, managing git commits for tasks, or understanding the verification protocol.

wshobson/agents · 35 tokens

meta-pre-commit-quality-gate

Run three quality gates (ruff + mypy + pytest) in parallel over the staged diff, then arbitrate a single BLOCK/APPROVE verdict. Use before committing changes locally when you want a comprehensive pre-commit gate beyond per-file linting — exactly the same gate set CI enforces.

opensquilla/opensquilla · 68 tokens

Tanda-Workforce-MCP-Server: Skill for Claude Code