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 skills/packmindhub/packmind/adding-ai-agent-rendering-systemnpx skills add PackmindHub/packmind --skill adding-ai-agent-rendering-systemgit clone --depth 1 https://github.com/PackmindHub/packmindWrote 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/packmindhub/packmind/adding-ai-agent-rendering-system)<a href="https://agentmods.dev/skills/packmindhub/packmind/adding-ai-agent-rendering-system"><img src="https://agentmods.dev/badge/skills/packmindhub/packmind/adding-ai-agent-rendering-system.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.00061 | $0.04210 |
| Opus 5 | $0.00030 | $0.02105 |
| Sonnet 5 | $0.00012 | $0.00842 |
| Haiku 4.5 | $0.00006 | $0.00421 |
Grade A, and why
adding-ai-agent-rendering-system 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.
How it starts
The opening of the file, as written. The whole thing — 418 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Add a new AI agent rendering system to Packmind, supporting both single-file (like AGENTS.md) and multi-file (like Cursor/Continue) patterns, including type definitions, deployer implementation, registry registration, frontend UI integration, documentation updates, and comprehensive tests following Packmind test standards.
When to Use
-
When adding support for a new AI coding assistant (e.g., Continue, Cursor, Claude Code, GitHub Copilot, OpenCode)
-
When implementing a new rendering format for standards and recipes distribution
-
When extending Packmind to support additional AI agent integrations
-
When creating a new deployer that follows the ICodingAgentDeployer interface
Prerequisites — Gather from User
Before proceeding, the following information must be known. If any of these are unclear or not provided, prompt the user to clarify before starting implementation.
-
What is the agent's identifier key and display name?
- The identifier key is the snake_case string used in code (
CodingAgenttype,CodingAgentsrecord,AGENT_FILE_PATHS, etc.). Examples:opencode,gitlab_duo,continue,agents_md. - The display name is the human-readable label shown in the frontend UI and CLI. Examples:
OpenCode,GitLab Duo,Continue,AGENTS.md. - Both values are reused consistently across all steps (type definitions, deployer class, registry, frontend labels, CLI display names, documentation).
- The identifier key is the snake_case string used in code (
-
In which directories will Standards be rendered?
- Multi-file example:
.agent/rules/(one file per standard) - Single-file example:
AGENTS.md,.agent/guidelines.md(all standards aggregated into one file) - Hybrid is possible (single-file standards + multi-file commands/skills)
- Multi-file example:
-
In which directories will Commands be rendered?
- If the agent supports native slash commands: provide the directory (e.g.,
.agent/commands/) - If the agent does NOT support native slash commands, say so explicitly. Commands will be deployed to
.packmind/commands/as a fallback (same pattern used by GitLab Duo, Junie, and AGENTS.md agents). Users invoke them via@.packmind/commands/command-name.md.
- If the agent supports native slash commands: provide the directory (e.g.,
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 · 418 lines · 61 tokens per session scan A 120336ae6b2b
adding-ai-agent-rendering-system is a skill published in the GitHub repository PackmindHub/packmind (308 stars, last pushed today), licensed Apache-2.0. It adds 61 tokens to every session and 4,210 once invoked, about $0.0003 per session on Opus 5. 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 skills, from other repositories
token-saver-config
Configure and diagnose token-saver compression settings. Use when the user asks about adjusting compression levels, checking processor status, debugging hook issues, or reviewing savings statistics.
sdd
Execute the Liatrio Spec-Driven Development (SDD) workflow when explicitly invoked by the user. NOTE: this skill is NOT intended to be dynamically loaded or automatically triggered; it should only ever be explicitly called by the user.
loadout-import-workflow
Import another repo's command/skill suite into loadout as a workflow. Use when the user points at an agent framework, plugin, or command pack (e.g. a GitHub repo, a .claude/commands/ directory, a skills pack) and wants its process turned into a loadout [[workflows]] entry — "import this workflow", "turn this plugin…
loadout-migrate
Migrate existing global AI agent instructions into loadout. Use when adopting loadout, importing a CLAUDE.md / AGENTS.md / global agent rules into loadout, setting up /.config/loadout/config.toml, or turning prose agent instructions into reusable fragments and stack-targeted profiles.
loadout-remember
Save a durable, cross-project user preference into loadout's global fragments/profiles — or update the fragment it contradicts. Use when the user states lasting guidance that should follow them across projects and agents ("always X", "never Y", "stop doing Z"), especially when it conflicts with guidance the loadout…
code-review
Plan-Forge-tuned comprehensive code review — runs public-surface diff, forge analysis, architecture / security / testing / patterns checks, plus Plan-Forge-specific gates (ACI compliance, dual-shell parity, branch model). Use before merging features or at the end of a phase. With --quorum, dispatches multi-model…