This directory contains repository-level GitHub Copilot custom agents for the Citizen Intelligence Agency platform. Each agent provides domain-specific expertise and enforces the Hack23 Information Security Policy (ISP) and its supporting ISMS policies.
Scope: These are repository-level agents (
.github/agents/*.md). Per Hack23 policy, repo-level agents do not declaremcp-servers:blocks — MCP configuration is handled by the environment via.github/copilot-mcp-config.json. All agents declaretools: ["*"]so the Copilot runtime can grant full tool access.
| Agent | Expertise | Primary Use |
|---|---|---|
| task-agent | Product quality, GitHub issues, Copilot orchestration, ISMS | Issue engineering, quality analysis, Copilot task delegation (base_ref, stacked PRs) |
| stack-specialist | Java 21/26, Spring, Vaadin, Hibernate/JPA, PostgreSQL 18, Maven 3.9.15 | Implementation, refactoring, debugging, SDLC security gates |
| ui-enhancement-specialist | Vaadin, data visualization, WCAG 2.1 AA, secure rendering, privacy-by-design | UI/UX improvements, charts, accessibility, XSS-safe components |
| intelligence-operative | Political science, OSINT, intelligence analysis, risk frameworks, Swedish politics | Analytical frameworks, data source integration, classified intelligence products |
| business-development-specialist | Strategic planning, partnerships, revenue models, market expansion | Business strategy, licensing, partner due-diligence |
| marketing-specialist | Digital marketing, content strategy, community building, brand positioning | Neutral, privacy-respecting storytelling; OSS posture marketing |
Agents are automatically available in GitHub Copilot conversations. Reference them by name:
@task-agent Analyze SonarCloud results and create prioritized improvement issues
@task-agent Assign issue #8033 to Copilot on branch feature/isp-integration with custom instructions
@stack-specialist How should I implement a new JPA entity for committee membership?
@ui-enhancement-specialist Review this Vaadin view for WCAG 2.1 AA compliance
@intelligence-operative Design a risk scoring framework for politician financial disclosures
@business-development-specialist Evaluate a partnership request from an academic institution
@marketing-specialist Draft a release announcement for the new risk dashboard
All agents follow these common principles:
- Context-aware — read
README.md,copilot-instructions.md,copilot-setup-steps.yml, andcopilot-mcp-config.jsonbefore work - ISP-first — the Hack23 Information Security Policy is the apex — every change defers to it
- Skills-integrated — reference the
.github/skills/library (80 skills, see skills README) - Evidence-based — recommendations grounded in data, metrics, scanner output, ISMS controls
- Security-first — align with Secure Development Policy, Open Source Policy, Secrets Management, Cryptography Policy, Access Control
- Classification-aware — every artefact is labelled per CLASSIFICATION
- Non-partisan — outputs analyse all parties / politicians with equal rigor
- Human-in-the-loop — Critical / High security changes require human approval
Every agent has explicit responsibility for specific ISMS policies. The Information Security Policy (ISP) is the apex for all.
| Policy | task-agent | stack-specialist | ui-enhancement | intelligence-operative | business-dev | marketing |
|---|---|---|---|---|---|---|
| Information Security Policy (Apex) | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Secure Development Policy | ✅ | ✅ | ✅ | ○ | ○ | ○ |
| Open Source Policy | ✅ | ✅ | ○ | ○ | ✅ | ✅ |
| Secrets Management Policy | ✅ | ✅ | ○ | ○ | ○ | ○ |
| Cryptography Policy | ○ | ✅ | ○ | ○ | ○ | ○ |
| Access Control Policy | ✅ | ✅ | ✅ | ○ | ○ | ○ |
| CLASSIFICATION | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Data Protection Policy | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Privacy Policy | ○ | ○ | ✅ | ✅ | ○ | ✅ |
| Vulnerability Management | ✅ | ✅ | ○ | ○ | ○ | ✅ |
| Change Management | ✅ | ✅ | ○ | ○ | ✅ | ○ |
| Third Party Management | ○ | ✅ | ○ | ○ | ✅ | ○ |
| Incident Response Plan | ✅ | ✅ | ○ | ✅ | ○ | ✅ |
| Threat Modeling | ✅ | ✅ | ✅ | ○ | ○ | ○ |
| AI Policy | ✅ | ✅ | ✅ | ✅ | ✅ | ✅ |
| Information Security Strategy | ○ | ○ | ○ | ✅ | ✅ | ✅ |
Legend: ✅ primary owner / must comply · ○ secondary / consult as needed
For the full 80-skill library, see .github/skills/README.md.
hack23-information-security-policy,hack23-isms-compliance,secure-development-policy,open-source-policyvulnerability-management,code-quality-checks,testing-strategy-enforcement,product-quality-analysisissue-triage-workflow,product-management-patternsplaywright-ui-testing,accessibility-wcag-patternsgithub-actions-workflows,github-agentic-workflows,ai-governance
hack23-information-security-policy,secure-development-policy,secrets-management,cryptography-policyspring-framework-patterns,jpa-hibernate-optimization,postgresql-operationsmaven-build-management,github-actions-workflows,ci-cd-securityunit-testing-patterns,integration-testing,performance-optimization,api-integrationsecure-code-review,input-validation,threat-modeling,vulnerability-management
hack23-information-security-policy,secure-development-policyvaadin-component-design,ui-ux-design-systemaccessibility-wcag-patterns,data-visualization-principles,advanced-data-visualizationplaywright-ui-testing,e2e-testing,input-validationdata-protection,gdpr-compliance,classification-framework-enforcement,performance-optimization
hack23-information-security-policyswedish-political-system,political-science-analysis,electoral-analysis,legislative-monitoringosint-methodologies,intelligence-analysis-techniques,behavioral-analysisrisk-assessment-frameworks,risk-assessment-methodology,strategic-communication-analysis,data-science-for-intelligencedata-protection,gdpr-compliance,classification-framework-enforcement,ai-governanceeuropean-parliament-api,cia-data-integration
hack23-information-security-policy,information-security-strategybusiness-model-canvas,product-management-patternsopen-source-policy,compliance-frameworks,hack23-isms-compliancegdpr-compliance,data-protection,cia-data-integration,european-parliament-api
hack23-information-security-policyseo-best-practices,documentation-standards,contribution-guidelinesopen-source-policy,data-visualization-principles,accessibility-wcag-patternsgdpr-compliance,data-protection,ai-governance
Each repository-level agent file uses this structure:
---
name: agent-name # kebab-case, unique
description: One-sentence role summary (≤200 chars)
tools: ["*"] # always allow all tools
---
# Role header + mission
**Always read first:** …context files…
## Core Expertise
## ISMS Policy Integration ← explicit mapping table
## (Domain-specific sections)
## Agent Handoff Matrix ← who to delegate to
## Boundaries — Must NOT Do ← red-lines
## Skills I Primarily Use
## Remember ← bullet key remindersRepository agents do not include
mcp-servers:. MCP configuration lives in.github/copilot-mcp-config.jsonand is applied by the Copilot runtime.
- Skills Library — 80 strategic skills for security, testing, architecture, compliance, intelligence
- Copilot Instructions — Global coding standards and ISMS integration
- Copilot MCP Config — MCP server configuration (environment-level)
- README — Project overview and documentation
- Hack23 Information Security Policy (Apex)
- Hack23 ISMS-PUBLIC — All Hack23 ISMS policies