agentmods.dev

accessibility-agents: Skill for Gemini CLI

.gemini/extensions/a11y-agents/skills/template-builder/SKILL.md

Template Builder is a skill for Gemini CLI from Community-Access/accessibility-agents. It costs 36 tokens per session (2,736 once invoked), scanned A, original, MIT.

A guided tool for creating GitHub issue, pull request, and discussion templates without writing the YAML configuration by hand. It asks questions and generates templates you can place in a repository.

In plain words
What is it for?
Use it to create structured templates for bug reports, feature requests, pull requests, and discussions.
Why use it?
It reduces the effort and mistakes involved in designing and formatting GitHub contribution forms.

Skill for Gemini CLI

Written for Gemini CLI: installed under .gemini/.

This is Community-Access/accessibility-agents's own configuration. It tells Gemini CLI how to work on accessibility-agents itself, so it is not a mod to install elsewhere. Copy it as a starting point and replace the rules that are about this project. Everything accessibility-agents configures →

not rated 405repo +2 26d ago A scan 36 tokens original MIT
View source ↗ Community-Access/accessibility-agents
Reuse

Borrowing it

Nothing to install: this file belongs to Community-Access/accessibility-agents. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file
curl -O https://raw.githubusercontent.com/Community-Access/accessibility-agents/main/.gemini/extensions/a11y-agents/skills/template-builder/SKILL.md
Clone the repo
git clone --depth 1 https://github.com/Community-Access/accessibility-agents

Made for: Gemini CLI.

Wrote 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.

agentmods badge for Template Builder

README.md
[![agentmods](https://agentmods.dev/badge/skills/community-access/accessibility-agents/template-builder.svg)](https://agentmods.dev/skills/community-access/accessibility-agents/template-builder)
Your own site
<a href="https://agentmods.dev/skills/community-access/accessibility-agents/template-builder"><img src="https://agentmods.dev/badge/skills/community-access/accessibility-agents/template-builder.svg" alt="Measured on agentmods" height="20"></a>
Per session 36 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,736 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00036 $0.02736
Opus 5 $0.00018 $0.01368
Sonnet 5 $0.00007 $0.00547
Haiku 4.5 $0.00004 $0.00274

Measured 3d ago against content hash dcdaea8c3b6c, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-07, from the pricing page.

Security

Grade A, and why

Template Builder 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 3d 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.

.gemini/extensions/a11y-agents/skills/template-builder/SKILL.md · 331 lines

How it starts

The opening of the file, as written. The whole thing — 331 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Template Builder Agent

Shared instructions

Skills: github-workflow-standards, github-scanning

A magical interactive agent that guides you through building GitHub issue templates step-by-step using VS Code's Ask Questions feature. Instead of writing YAML, answer simple questions and the agent generates the template for you.

How to Use

In VS Code

  1. Open Copilot Chat (Ctrl+Shift+I Windows, Cmd+Shift+I macOS)
  2. Type: @template-builder or /build-template
  3. The agent will ask you a series of questions to understand your template
  4. Answer each question in the Ask Questions prompts
  5. The agent generates your complete YAML template
  6. Copy the output to .github/ISSUE_TEMPLATE/your-template-name.yml

In GitHub Web

  1. Open Copilot Chat (Copilot button in top right)
  2. Mention: @template-builder
  3. Type your template goals (e.g., "I want to build an accessibility bug report template")
  4. The agent provides step-by-step YAML scaffolding you can copy and refine

Example Workflow

You: @template-builder create accessibility bug template

Agent asks (via Ask Questions):

  1. Template name? -> You answer: "Accessibility Bug Report"
  2. What's this template for? -> "Report screen reader and keyboard issues"
  3. First field? -> "Screen Reader (dropdown)"
  4. Dropdown options? -> "NVDA, JAWS, VoiceOver, Other"
  5. Is it required? -> "Yes"
  6. Next field? -> "Browser (dropdown)" ... (continues for each field)

Agent outputs: Complete YAML template ready to paste

Template Builder Guide: Step-by-Step

Phase 1: Gather Template Metadata

The agent starts by asking core questions about your template:

Questions:

  • What is the template name? (e.g., "Bug Report", "Feature Request", "Accessibility Issue")
  • One-line description of this template's purpose
  • Default title prefix for issues (e.g., "[BUG]", "[A11Y]", "[FEAT]")
  • What labels should this template auto-apply? (comma-separated)

Read the full file on GitHub · 331 lines

Changes

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.

  1. 3d ago First seen · 331 lines · 36 tokens per session scan A dcdaea8c3b6c

Subscribe to this mod's changes

Template Builder is a skill published in the GitHub repository Community-Access/accessibility-agents (405 stars, last pushed 26d ago), licensed MIT. It adds 36 tokens to every session and 2,736 once invoked, about $0.0002 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.

Git and workflowProductivitya11yaccessibilityai-agentsariaassistive-technologyclaude
Related

Other skills, from other repositories

Accessibility Auditor

Comprehensive WCAG 2.1 AA compliance testing combining automated axe-core scans with manual keyboard navigation, screen reader compatibility, and focus management verification.

PramodDutta/qaskills · 32 tokens

Accessibility A11y Enhanced

Comprehensive WCAG compliance and accessibility testing covering ARIA, keyboard navigation, screen readers, color contrast, and automated a11y validation.

PramodDutta/qaskills · 34 tokens

accessibility

Use when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast, tap-target size. NOT palette or visual intent (that is design), NOT test-runner setup (that is testing-web), NOT LCP/page-speed (that is…

ericrisco/rsc-harness · 86 tokens

accessibility-expert

Build interfaces usable by everyone: WCAG 2.2 conformance, semantic HTML, ARIA, keyboard navigation, screen readers and accessible forms. Use when the user mentions accessibility, a11y, WCAG, ARIA, screen readers, keyboard navigation, colour contrast, focus management, the European Accessibility Act or Section 508, or…

personamanagmentlayer/pcl · 98 tokens

game-accessibility-engineer

!cat skills/shared/game-visual-foundations.md 2>/dev/null || echo "=== Visual Foundations not loaded ===" !cat skills/shared/protocols/ux-protocol.md 2>/dev/null || true !cat skills/shared/protocols/input-validation.md 2>/dev/null || true !cat skills/shared/protocols/tool-efficiency.md 2>/dev/null || true !cat…

buiphucminhtam/forgewright · 73 tokens

accessibility-engineer

You are the Accessibility Engineering Specialist. You ensure digital products are usable by everyone, including people with visual, auditory, motor, and cognitive disabilities. You audit against WCAG 2.2 standards (AA minimum, AAA preferred), implement ARIA patterns, ensure keyboard navigability, test with screen…

buiphucminhtam/forgewright · 61 tokens