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 agents/antgroup/vsag/filing-issuesgit clone --depth 1 https://github.com/antgroup/vsagWrote 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/antgroup/vsag/filing-issues)<a href="https://agentmods.dev/agents/antgroup/vsag/filing-issues"><img src="https://agentmods.dev/badge/agents/antgroup/vsag/filing-issues.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.00555 |
| Opus 5 | $0.00000 | $0.00278 |
| Sonnet 5 | $0.00000 | $0.00111 |
| Haiku 4.5 | $0.00000 | $0.00056 |
Grade A, and why
filing-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 today.
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.
How it starts
The opening of the file, as written. The whole thing — 49 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Filing Issues With An Agent
Agents are expected to help users file high-quality issues. The full step-by-step workflow is not duplicated here — it lives in a single canonical file shared across Claude Code, OpenCode, and Codex:
Canonical workflow:
.github/agent-prompts/create-issue.mdWriting rules / template guide:
.github/ISSUE_TEMPLATE/ISSUE_GUIDE.md
The per-agent slash-command wrappers point at the canonical file:
.claude/commands/create-issue.md.opencode/command/create-issue.md.codex/prompts/create-issue.md
A shell wrapper is provided at tools/issue-helper/new-issue.sh
for users who prefer not to drive the agent's slash command directly.
Quick rules (must hold regardless of agent)
- Map every required field of the chosen YAML template under
.github/ISSUE_TEMPLATE/. Use// TODOfor genuinely unknown values. - Cite sources as
path:linefor repo references and full URLs forvsag.io/docspages. - Run
gh issue list --repo antgroup/vsag --search ... --state all --limit 5and append the matches under a## Related issuessection. Do not block creation on duplicates; the maintainers will close as needed. - Append a footer of the form
_Drafted with AI assistant: <AgentName>:<ModelVersion>_for transparency. Do not addSigned-off-by:to issues — DCO applies only to commits. - Show a dry-run preview and only call
gh issue createafter the user confirms. On failure, fall back togh issue create --web.
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.
- today First seen · 49 lines · 0 tokens per session scan A 9474fbb3fc78
filing-issues is an agent published in the GitHub repository antgroup/vsag (507 stars, last pushed today), licensed Apache-2.0. It costs nothing until one of its globs matches a file; then it loads 555 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-09-03.
Other agents, from other repositories
project-implementer
Implementation specialist - executes tasks from plans with TDD methodology, writes tests, and validates acceptance criteria. Use for executing phased implementation plans generated by attune:plan.
onboard-guide
Onboarding assistant that provides ongoing personalized guidance after initial /onboard. Use for questions about conventions, architecture, patterns, or "where do I put this?" — answers are tailored to the engineer's background.
scrum-master
Scrum Master agent (Bob) — generates story files from Epic Manifest rows and the delivery file.
Orchestrator
Task coordination and agent delegation.
project-manager
Project manager for CrawlForge MCP Server development. Coordinates tasks, delegates to specialized sub-agents IN PARALLEL, tracks progress, and ensures clean implementation. Use PROACTIVELY for any multi-step project coordination.
nexus
Turn one user task into a coherent, verified integration-branch delivery by coordinating the smallest safe adaptive workflow.