Borrowing it
Nothing to install: this file belongs to abetoluwani/linkedin-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.
curl -O https://raw.githubusercontent.com/abetoluwani/linkedin-mcp-server/main/.agents/skills/1-triage-issues/SKILL.mdgit clone --depth 1 https://github.com/abetoluwani/linkedin-mcp-serverWrote 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/abetoluwani/linkedin-mcp-server/1-triage-issues)<a href="https://agentmods.dev/skills/abetoluwani/linkedin-mcp-server/1-triage-issues"><img src="https://agentmods.dev/badge/skills/abetoluwani/linkedin-mcp-server/1-triage-issues/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/abetoluwani/linkedin-mcp-server/1-triage-issues"><img src="https://agentmods.dev/badge/skills/abetoluwani/linkedin-mcp-server/1-triage-issues.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.00138 | $0.01747 |
| Opus 5 | $0.00069 | $0.00873 |
| Sonnet 5 | $0.00028 | $0.00349 |
| Haiku 4.5 | $0.00014 | $0.00175 |
Grade A, and why
1-triage-issues 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 11d 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.
This is a copy
100% identical to 1-triage-issues — 0 lines differ, which has more behind it and is treated as the original. This page carries a canonical link to it rather than competing with it.
How it starts
The opening of the file, as written. The whole thing — 99 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Triage Open Issues and PRs
Goal: in one pass, turn the live state of stickerdaniel/linkedin-mcp-server into a maintainer-grade priority list. Read-only. No checkout, no edits, no reproduction. Reproduction belongs in /2-repro-issue; PR verification in /3-verify-pr-fix.
Inputs
$ARGUMENTS is optional. If set, treat as a label name (bug, enhancement) or freetext filter to narrow the scope. Otherwise scan everything open.
Phase 1 — Gather
REPO=stickerdaniel/linkedin-mcp-server
# Issues (gh calls the reactions field `reactionGroups`, not `reactions`)
gh issue list --repo $REPO --state open --limit 200 \
--json number,title,labels,createdAt,updatedAt,author,comments,reactionGroups,body
# PRs
gh pr list --repo $REPO --state open --limit 100 \
--json number,title,labels,createdAt,updatedAt,author,mergeable,mergeStateStatus,statusCheckRollup,additions,deletions,changedFiles,reviewDecision,isDraft,headRepositoryOwner
# Cross-link issues ↔ PRs via body references
gh search prs --repo $REPO --state open --json number,body,title --limit 100
Build a map issue_number → [referencing_pr_numbers] by scanning PR bodies for Closes #, Fixes #, Resolves #, plain #N.
If $ARGUMENTS is given, filter both lists down before scoring.
Phase 2 — Score each issue
For every open issue, compute four signals. Cite the evidence inline so the user can audit.
- Severity (1–5):
5= data loss / broken-for-all-users / security;4= core tool unavailable (e.g.get_person_profilereturning empty);3= degraded output for a subset (locale, edge-case profile);2= annoyance / cosmetic;1= question / docs. Read the body + labels (bug,critical,security,regression). - Reach (1–5): comment count, distinct commenters,
+1/👍reactions, references from other issues. - Age vs activity:
createdAt→ days old;updatedAt→ days since last activity. Stale-but-high-severity ranks higher than fresh-but-cosmetic. - Has fix in flight: did anyone open a PR (look up in cross-link map)? Is that PR ready to merge?
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.
- 11d ago First seen · 99 lines · 138 tokens per session scan A 4d947111aab8
1-triage-issues is a skill published in the GitHub repository abetoluwani/linkedin-mcp-server (0 stars, last pushed 21d ago), licensed Apache-2.0. It adds 138 tokens to every session and 1,747 once invoked, about $0.0007 per session on Opus 5. A static security scan graded it A with 0 findings. It is 100% identical to 1-triage-issues, differing in 0 lines, and is treated as a copy.
Other skills, from other repositories
pr-review-triage
Watch open PRs, check CI status, review staleness, merge conflicts, and unanswered review comments. Produces a prioritized watchlist.
issue-creation
Trigger: issue creation, bug reports, feature requests, or issue approval. Create and triage GitHub issues from repository evidence.
sdd-tasks
Break an SDD change into implementation tasks. Trigger: orchestrator launches task planning for a change.
systemic-issue-triage
Trigger: new issue, bug report, triage, backlog, issue flood, community report, root cause, dead-end, blocked user. Attack issues by root class, never one-by-one; fixes must shrink the system, not grow it.
spec-kitty-runtime-review
Review runtime-owned outputs using the Spec Kitty review workflow surface, then direct approval or rejection with structured feedback. Triggers: "review this work package", "check runtime output", "approve this step", "review WP", "is this WP ready to approve", "check this implementation". Does NOT handle: setup-only…
tech-debt
Track, categorize, and prioritize technical debt across the codebase. Scans for debt indicators, maintains a debt register, and recommends repayment scheduling.