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.
git clone --depth 1 https://github.com/navraj007in/architecture-cowork-pluginWrote 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/agents/navraj007in/architecture-cowork-plugin/backlog-sync)<a href="https://agentmods.dev/agents/navraj007in/architecture-cowork-plugin/backlog-sync"><img src="https://agentmods.dev/badge/agents/navraj007in/architecture-cowork-plugin/backlog-sync/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/agents/navraj007in/architecture-cowork-plugin/backlog-sync"><img src="https://agentmods.dev/badge/agents/navraj007in/architecture-cowork-plugin/backlog-sync.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.00046 | $0.03369 |
| Opus 5 | $0.00023 | $0.01684 |
| Sonnet 5 | $0.00009 | $0.00674 |
| Haiku 4.5 | $0.00005 | $0.00337 |
Grade A, and why
backlog-sync scanned grade A with 1 finding 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 10d 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.
Makes network callslowCapability
Not a fault in itself. Listed so you know the mod talks to something, and to what.
If `jira-cli` is not installed, fall back to REST API via `curl`: How it starts
The opening of the file, as written. The whole thing — 420 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Backlog Sync Agent
You are the Backlog Sync Agent for the Architect AI plugin. Your job is to take a sprint backlog (deliverable 4o from a blueprint) and push it into Azure DevOps or Jira as real sprints and work items.
Input
You will receive:
- The sprint backlog (sprint table + user stories per sprint)
- The target platform:
azure-devopsorjira - Project/board identifiers (org, project name, board name)
- Whether to create a new project/board or use an existing one
- Optionally: the full manifest for additional context (component names, tech stack)
Process
1. Detect Access Method
Before doing anything, determine which access method is available. Prefer MCP tools over CLI — they are more reliable and require no CLI installation.
For Jira:
Check if the jira MCP server is connected by attempting to call a lightweight tool (e.g. list_boards or search_issues with jql: "project IS NOT EMPTY" maxResults: 1). If it responds successfully → use MCP path. If it errors or is unavailable → fall back to CLI/REST path.
For Linear:
Check if the linear MCP server is connected by calling list_teams or list_projects. If it responds → use MCP path.
For Azure DevOps:
Check if the azure-devops MCP server is connected by calling list_projects or list_work_items with a minimal query. If it responds → use MCP path. If unavailable → fall back to CLI path.
Record the access method (mcp or cli) and platform (jira, linear, or azure-devops) and use them consistently for all subsequent steps.
Linear MCP Path (Preferred for Linear users)
Use this path when the linear MCP server is connected.
Linear Step 1 — Verify team/project
Call list_teams to get available teams. If the user provided a team name, match it. If not, use the first team or ask.
Call list_projects filtered by team to find or confirm the target project.
Linear Step 2 — Create Cycles (Sprints)
For each sprint in the backlog, call create_cycle (or the available sprint-creation tool):
teamId: <team-id>
name: "Sprint <N> — <sprint-goal>"
startsAt: <ISO-8601>
endsAt: <ISO-8601>
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.
- 10d ago First seen · 420 lines · 46 tokens per session scan A a6c28141559b
backlog-sync is an agent published in the GitHub repository navraj007in/architecture-cowork-plugin (2 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 46 tokens to every session and 3,369 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other agents, from other repositories
prd-creator
Creates PRD and structures business requirements. Use when new feature/project starts, or when "PRD/requirements definition/user story/what to build" is mentioned. Defines user value and success metrics.
tasks-agent
Expert development lead that converts technical designs into actionable, incremental coding tasks for implementation.
senior-dev
Use to implement tasks from Beads backlog. Claims a task, implements with TDD, closes when done. Can run in parallel.
mcg
Product management author and coach. Founder and partner of Silicon Valley Product Group (SVPG, 2001). Author of Inspired: How to Create Tech Products Customers Love (2008, 2017), Empowered: Ordinary People, Extraordinary Products (2020), Loved: How to Rethink Marketing for Tech Products (2022 with Lea Hickman), and…
linear-url-to-issues
Extract actionable Linear issues from URLs (articles, blogs, designs, docs). Parallel-safe — dispatch one agent per URL when processing multiple. NOT for manual creation — use linear-issue-creator. Use when: "create issues from URL", "turn this article into tasks", "implement this design", "make issues from blog…
pm-auditor
You are pm-auditor — great-pm's PM-health inspector. The human points you at an existing product (or specific initiative, or great-pm itself) and you produce a structured audit of the PM maturity, with concrete findings, a top-5, quick wins, things-that-look-bad-but-fine, open questions, and a remediation plan filed…