Skip to content
Back to skills

Committer 2fa Audit

ASecurity

Audit source-control organization settings for strong 2FA/MFA requirements across all committers

  • 207 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 27, 2026
data-aigoshellbashgitapisecurity

Works with

  • api

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add jmagly/aiwg --skill committer-2fa-audit --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Committer 2fa Audit?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Committer 2fa Audit
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jmagly-committer-2fa-audit/badge)](https://www.skillsdirectory.com/skills/jmagly-committer-2fa-audit)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
namespace: aiwg
name: committer-2fa-audit
platforms: [all]
description: Audit source-control organization settings for strong 2FA/MFA requirements across all committers
requires:
  - tracker-platform: github or gitea
  - token: org-admin token when querying member 2FA status
ensures:
  - report: committer 2FA enforcement status and platform setting guidance
errors:
  - token-missing: org-admin token required for platform member audit
  - unsupported-platform: selected tracker does not expose 2FA enrollment status
invariants:
  - tokens are never printed, written, or passed through shell history
  - recovery codes are never requested
commandHint:
  argumentHint: "[--platform github|gitea] [--org <name>] [--report-only]"
  allowedTools: Read, Bash
  model: sonnet
  category: security
  orchestration: false
---

# Committer 2FA Audit

Audit whether all committers are covered by strong two-factor authentication policy. This enforces `committer-2fa-required` and maps curl Practice 25 into source-control governance.

## GitHub

Requires an org-admin token supplied outside the prompt context. Query the org member endpoint with the 2FA-disabled filter and report non-compliant users.

## Gitea

Gitea support is instance-dependent. When the API exposes 2FA status, report non-compliant users. When it does not, report the configured organization/site policy and mark member-level visibility as unavailable.

## Token Handling

Follow `token-security`: read tokens from a secure environment or secret manager, do not echo them, do not paste them into issue comments, and do not persist audit responses containing token material.

## References

- `agentic/code/frameworks/security-engineering/rules/committer-2fa-required.md`
- `agentic/code/addons/aiwg-utils/rules/token-security.md`

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…