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.
npx agentmods add commands/cognigy/cognigy-plugin/pr-templategit clone --depth 1 https://github.com/Cognigy/cognigy-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/commands/cognigy/cognigy-plugin/pr-template)<a href="https://agentmods.dev/commands/cognigy/cognigy-plugin/pr-template"><img src="https://agentmods.dev/badge/commands/cognigy/cognigy-plugin/pr-template.svg" alt="Measured on agentmods" 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 | $0.00000 | $0.00451 |
| Opus 5 | $0.00000 | $0.00226 |
| Sonnet 5 | $0.00000 | $0.00090 |
| Haiku 4.5 | $0.00000 | $0.00045 |
Grade A, and why
pr-template 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 4d 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.
What it actually says
Generate a pull request description for the current branch by analyzing all commits and changes since diverging from main.
Steps
-
Run these commands in parallel to gather context:
git log main..HEAD --oneline— list commits on this branchgit diff main...HEAD --stat— files changed summarygit diff main...HEAD— full diff for content analysis
-
Analyze the changes and determine:
- What type of change this is (feature, fix, refactor, docs, chore, release)
- Which tools, APIs, or components are affected
- Whether any breaking changes or migration steps are needed
-
Output the PR description inside a single fenced code block (
```md ... ```) so the user can copy-paste it directly. The content inside the code block must follow this template exactly:
## Summary
- <bullet summarizing the main change — lead with the verb: Add, Fix, Update, Remove, Refactor>
- <additional bullet if there are secondary changes>
- <optional: note any breaking changes or migration required>
## Changes
| File / Component | Description |
| --------------------- | ---------------------- |
| `<file or component>` | <what changed and why> |
| `<file or component>` | <what changed and why> |
## Test plan
Automated — CI runs tests and Prettier checks on every PR via `.github/workflows/pr.yml`.
- After the code block, suggest a PR title (under 70 characters) on its own line.
Guidelines
- Use present tense imperative verbs: "Add", "Fix", "Update", "Remove"
- The Summary section should answer "what and why", not "what files changed"
- The Changes table is the "what files" detail layer — use a markdown table so it renders cleanly on GitHub
- The Test plan section should reference the automated CI checks, not manual steps
- If the diff is large, group related changes in the Changes table
- Flag any changes that affect the marketplace submission requirements (LICENSE, manifest.json, README, tool annotations, privacy policy)
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.
- 4d ago First seen · 46 lines · 0 tokens per session scan A 7ae890ec47e5
pr-template is a command published in the GitHub repository Cognigy/cognigy-plugin (12 stars, last pushed yesterday), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 451 tokens. 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 commands, from other repositories
git
Git operations with intelligent commit messages and workflow optimization.
checklist
Generate a custom checklist for the current feature based on user requirements.
clarify
Identify underspecified areas in the current feature spec by asking up to 5 highly targeted clarification questions and encoding answers back into the spec.
specify
Create or update the feature specification from a natural language feature description.
converge
Assess the current codebase against the feature's spec, plan, and tasks, then append any remaining unbuilt work as new tasks to tasks.md so implement can complete it.
implement
Execute the implementation plan by processing and executing all tasks defined in tasks.md.