Getting it into your agent
It runs from inside its repository, so the clone comes first — what it calls does not travel with the file alone.
git clone --depth 1 https://github.com/tikalk/adlc-team-skillsnpx agentmods add skills/tikalk/adlc-team-skills/team-constitutionWrote 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/tikalk/adlc-team-skills/team-constitution)<a href="https://agentmods.dev/skills/tikalk/adlc-team-skills/team-constitution"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/team-constitution/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/tikalk/adlc-team-skills/team-constitution"><img src="https://agentmods.dev/badge/skills/tikalk/adlc-team-skills/team-constitution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
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.1 | $0.00036 | $0.03080 |
| Opus 5.5 | $0.00014 | $0.01232 |
| Sonnet 5.5 | $0.00007 | $0.00616 |
| Haiku 4.5 | $0.00004 | $0.00308 |
Grade A, and why
team-constitution 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 25d 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 — 302 lines — stays where its author put it; the contents beside it link to each section on GitHub.
team-constitution
What this skill does
Interactively create or amend the team constitution at {TEAM_AI_DIRECTIVES}/context_modules/constitution.md.
The scaffold written by team-setup (Mode 3) contains only a placeholder ("No team-wide principles defined yet"). This skill turns that placeholder into a real constitution through guided elicitation:
- Propose principles informed by team context (existing rules, CDRs, AGENTS.md)
- Review each principle interactively — confirm, edit, or reject
- Write the constitution in the established team format (OKF v0.2 frontmatter + numbered principles + Governance section)
What this skill is NOT:
- Not a port of spec-kit's
spec.constitutiontemplate machinery — no placeholder tokens, no hooks, noextensions.yml, no template propagation, no Sync Impact Report - Not semantic versioning — the team constitution is versioned by git history in the team AI directives repo; freshness is tracked by OKF v0.2 frontmatter (
generated,verified,stale_after) via/team-repair - Not for project-level constitutions (
docs/adlc/memory/constitution.md, legacy.adlc/memory/constitution.mdfallback) — those remainspec.constitutionterritory when spec-kit is in play
When to use
- After
team-setupMode 3: the scaffold wrote a placeholder constitution — fill it with real principles - New team AI directives (cloned or existing): constitution is missing or still a placeholder
- Amending principles: the team wants to add, reword, or remove principles
When NOT to use
- Project-level constitution: use spec-kit's
spec.constitutionfordocs/adlc/memory/constitution.md(legacy.adlc/memory/constitution.mdfallback) - Constitution changes via CDR flow: if a constitution change was proposed as a CDR, let
/team-leveluphandle it - team AI directives not configured: run
/team-setupfirst
Process
User Input
$ARGUMENTS
You MUST consider the user input before proceeding (if not empty).
What ships with it
2 files beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.
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.
- 25d ago Changed 26d3e70ed965
- 1mo ago Changed 8331e72c500e
- 1mo ago Changed · -8 tokens per session e40c7b594d95
- 1mo ago First seen · 302 lines · 44 tokens per session scan A e46523d7fd8e
team-constitution is a skill published in the GitHub repository tikalk/adlc-team-skills (143 stars, last pushed today), licensed MIT. It adds 36 tokens to every session and 3,080 once invoked, about $0.0001 per session on Opus 5.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
building-agents
Use when building or restructuring an LLM agent — provider adapter, tool calling, structured output, RAG, agent loop, eval gate, cost routing, tracing, MCP server — model-agnostic across OpenAI/Anthropic/Gemini/OSS so a model swap is a config change. NOT vector-store SQL alone (that is postgresdb) or service…
agent-eval
Use when measuring whether an LLM or agent system actually got better and gating merges on it: golden sets, fixing an inflated LLM-as-judge, scoring RAG (faithfulness, contextual recall) or agent trajectories (tool correctness, completion), or picking an eval framework. NOT building the agent loop, tools or RAG…
decision-records
Use when a hard-to-reverse choice (database, framework, vendor, auth model) must be frozen as an immutable numbered ADR — the context that forced it, the options weighed, the decision, consequences both ways — or superseded without erasing history. NOT a meeting recap (that is meeting-notes), NOT standing project…
prompt-engineering
Use when one prompt must give the same right answer across reruns, models, and pasted-in hostile input: forcing a fixed schema, picking the few-shot set, ordering the prompt blocks, or the inline cases you run while tuning. NOT the agent loop, tools, or retrieval (that is building-agents), NOT a standing CI eval…
respect-the-oracle
Use when working against a test suite, spec, or graded harness you do not own - especially inside an automated loop scored on how many tests pass - and tempted to change the tests, weaken assertions, hardcode expected outputs, special-case inputs, or overfit the visible examples to turn things green.
refocusing
Use when a long-running agent may have lost the product outcome, when context was compacted, when work has crossed a major boundary, or when a fresh path-based trace is needed before the next consequential action. Not for fresh-session orientation, waking an idle seat, or checkpoints.