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.
/plugin marketplace add tqnonline/agent-forgenpx agentmods add plugins/tqnonline/agent-forge/pmgit clone --depth 1 https://github.com/tqnonline/agent-forgeGrade A, and why
pm 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.
What it actually says
{
"name": "pm",
"description": "Product and Program Management skill suite for technology industries. 12 composable skills following UNIX philosophy: philosophy, discover, map, tom-architect, epic-decompose, prd-draft, prd-validate, prd-review, backlog-decompose, backlog-ado, backlog-linear, backlog-github. Includes Product Constitution (living strategy doc), multi-platform TOM design, and 11-Star PRD quality framework. Works for SaaS product companies and consulting delivery firms.",
"version": "2.2.0",
"author": {
"name": "Rahul Narasimha Akmol",
"email": "[email protected]"
},
"mcp_dependencies": {
"linear": {
"description": "Linear MCP server for direct issue creation, listing, and project/team management",
"required_tools": [
"save_issue",
"list_issues",
"list_projects",
"list_teams",
"get_issue",
"create_issue_label",
"list_issue_labels",
"list_issue_statuses"
],
"usage": "backlog-linear"
},
"github": {
"description": "GitHub MCP server for issue creation, sub-issue hierarchy, and search",
"required_tools": [
"issue_write",
"issue_read",
"list_issues",
"search_issues",
"sub_issue_write",
"list_issue_types",
"add_issue_comment"
],
"usage": "backlog-github"
}
}
}
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 · 39 lines scan A 9b617a7f2fd1
pm is a plugin published in the GitHub repository tqnonline/agent-forge (2 stars, last pushed 3mo ago), licensed BSD-3-Clause. Its token cost is not measured: this kind of file is read by the harness, not the model. 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.
Other plugins, from other repositories
jira-assistant-skills
Plugin marketplace listing 1 plugin: jira-assistant-skills.
beans-prime
Configure Claude Code to track work using Beans.
rook-claude
Claude Code plugins for rook (github.com/rook/) maintainers: maintainer-grade code review, backlog triage, systemic-PR campaigns, and rook house conventions.
rook-maintainer
Maintainer-grade skills for rook (github.com/rook/): code review, backlog triage, systemic-PR campaigns, and the rook house conventions they enforce.
ai-skills
Plugin marketplace listing 8 plugins: security-hooks, pr-review-triage, dev-skills, nix-skills, git-workflow.
workbench
Ticket-to-PR development workflow: triage, plan with verified citations, implement inside the plan, review, commit, PR. Pluggable issue trackers (Jira, Azure DevOps, GitHub Issues) or a backlog in the repo, so it works with no tracker at all.