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/davidroliverba/architectkb/formnpx skills add DavidROliverBA/ArchitectKB --skill formgit clone --depth 1 https://github.com/DavidROliverBA/ArchitectKBWrote 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/davidroliverba/architectkb/form)<a href="https://agentmods.dev/skills/davidroliverba/architectkb/form"><img src="https://agentmods.dev/badge/skills/davidroliverba/architectkb/form.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.00006 | $0.01033 |
| Opus 5 | $0.00003 | $0.00517 |
| Sonnet 5 | $0.00001 | $0.00207 |
| Haiku 4.5 | $0.00001 | $0.00103 |
Grade A, and why
form 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.
How it starts
The opening of the file, as written. The whole thing — 157 lines — stays where its author put it; the contents beside it link to each section on GitHub.
/form Skill
Quick-create a form submission tracking note.
Usage
/form DPIA MyDataIntegration
/form CyberRisk "MaintenanceSystem"
/form TPRM VendorTooling
/form IAF "AIIncidentProcessor"
/form ChangeRequest OpDef
Instructions
-
Parse arguments:
- First word = formType
- Remaining = project name (handle quotes for multi-word)
-
Validate formType against allowed values:
- DPIA
- CyberRisk
- TPRM
- IAF
- ChangeRequest
- Other
-
Find matching project (fuzzy match):
- Search for
Project - *{{project}}*.md - If not found, ask user to confirm project name
- Search for
-
Create form submission note:
Filename:
Form Submission - {{formType}} for {{project}}.mdLocation: Root directory (same as other content notes)
-
Populate frontmatter:
---
type: FormSubmission
title: "{{formType}} for {{project}}"
formType: { { formType } }
status: draft
project: "[[Project - {{project}}]]"
requestingTeam: { { lookup from table below } }
submittedDate: null
responseDate: null
expiryDate: null
referenceNumber: null
attachments: []
created: { { today } }
modified: { { today } }
tags: [activity/compliance, { { domain_tag } }] # See tag lookup table below
---
- Requesting team and tag lookup:
| formType | requestingTeam | domain_tag |
|---|---|---|
| DPIA | Data Privacy | domain/data |
| CyberRisk | Cyber Security | domain/security |
| TPRM | Procurement | domain/security |
| IAF | Cyber Delivery Assurance | domain/security |
| ChangeRequest | Change Management | domain/operations |
| Other | (ask user) | (ask user) |
- Generate body content:
# {{formType}} for {{project}}
## Form Details
| Field | Value |
| ------------------- | ------------------------- |
| **Form Type** | {{formType}} |
| **Status** | draft |
| **Project** | [[Project - {{project}}]] |
| **Requesting Team** | {{requestingTeam}} |
| **Submitted** | - |
| **Response** | - |
| **Reference** | - |
## Summary
<!-- Brief description of what this form submission covers -->
## Key Information Provided
<!-- Main points you included in the form -->
- System/service name:
- Data classification:
- Third parties involved:
- Key risks identified:
## Attachments
<!-- Link screenshots or PDFs of the submitted form here -->
<!-- Example: ![[+Attachments/dpia-screenshot.png]] -->
## Response / Outcome
<!-- What was the result? Any conditions or follow-up required? -->
## Notes
<!-- Any additional context or follow-up actions -->
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 · 157 lines · 6 tokens per session scan A e984b1d46f6c
form is a skill published in the GitHub repository DavidROliverBA/ArchitectKB (52 stars, last pushed 6mo ago), licensed MIT. It adds 6 tokens to every session and 1,033 once invoked, about $0.0000 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-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…