Borrowing it
Nothing to install: this file belongs to Doyajin174/teguma. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Doyajin174/teguma/main/AGENTS.mdgit clone --depth 1 https://github.com/Doyajin174/tegumaWrote 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/instructions/doyajin174/teguma/agents-md)<a href="https://agentmods.dev/instructions/doyajin174/teguma/agents-md"><img src="https://agentmods.dev/badge/instructions/doyajin174/teguma/agents-md.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.1 | $0.02746 | $0.02746 |
| Opus 5 | $0.01373 | $0.01373 |
| Sonnet 5 | $0.00549 | $0.00549 |
| Haiku 4.5 | $0.00275 | $0.00275 |
Grade A, and why
teguma AGENTS.md 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 5d 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 — 257 lines — stays where its author put it; the contents beside it link to each section on GitHub.
teguma 운영환경
Figma 오픈소스 프로젝트 컬렉션. 이슈 기반 개발, 릴리스 관리, 자동화 리뷰를 따른다.
핵심 원칙
- 1 이슈 = 1 브랜치 = 1 워크트리 — 워크트리는 항상 깔끔하게 유지
- 작업 순서: 이슈 조사(인터넷 조사 포함) → 기획/명세 작성 → 구현 → PR → 리뷰 → 머지
- tidy: 레포 구조·거버넌스·문서 정비 시
tidy스킬 사용 - atlas: 코드 아틀라스 유지보수 시
maintain-code-atlas스킬 사용
브랜치·워크트리 규약
main ← 항상 릴리스 가능 상태
feat/<issue>-<slug>
fix/<issue>-<slug>
hotfix/<slug>
research/<slug> ← 조사 전용 (머지 안 할 수 있음)
- 워크트리 경로:
../teguma-wt/<branch-name> - 머지 후 워크트리 즉시 제거 (
git worktree remove) - main은 fast-forward 전용, force-push 금지
커밋 규약 (Conventional Commits)
feat: <summary> → minor
fix: <summary> → patch
docs: <summary>
chore: <summary>
refactor: <summary>
test: <summary>
perf: <summary>
breaking: <summary> → major
- 본문에
Closes #<issue>또는Refs #<issue>포함 - 1 커밋 = 1 논리 변경. WIP 커밋은 squash 전까지만 허용
1. 리뷰 절차
- 셀프 리뷰 —
git diff main...HEAD전체 읽기, 오타·디버그 코드·주석 처리 확인 - AI 리뷰 — 설계 원칙(SOLID, DRY, KISS)·엣지 케이스·명세 일치 여부 점검
- fixup — 지적 사항 반영,
git commit --fixup사용 - squash merge —
gh pr merge --squash --delete-branch
리뷰 체크리스트:
- 명세(spec)와 구현이 일치하는가
- 에러 핸들링·빈 입력·대형 입력 엣지 케이스
- 시크릿·개인정보 하드코딩 없음
- 테스트가 핵심 경로를 커버하는가
- 불필요한 의존성 추가 없음
2. 머지 후 루틴
git checkout main && git pull --ff-only
git worktree remove ../teguma-wt/<branch>
git branch -d <branch>
gh issue close <issue> # 또는 PR 머지가 자동 close
- 이슈 닫힘 확인 후 릴리스 판단 (아래 3번 참조)
- 마일스톤 진행률 갱신
3. 릴리스 체계
- semver 엄격 준수:
MAJOR.MINOR.PATCH - feat → minor, fix → patch, breaking → major
- CHANGELOG.md 자동 갱신 (Conventional Commits 기반)
- 릴리스 시 작성:
CHANGELOG.md항목- GitHub Release 노트 (What Changed / Breaking / Migration)
- 태그:
v<semver>
- 매 버전 업데이트 리포트 작성 →
docs/releases/v<version>.md
4. 핫픽스 절차
긴급 수정용 빠른 경로:
hotfix/<slug>브랜치를 main에서 생성- 명세 생략 가능, AI 리뷰 생략 가능
- 최소 셀프 리뷰(변경 diff 읽기)는 필수
- 머지 후 즉시 patch 릴리스
- 사후에 이슈 등록 + 회고 기록
5. 주간 회고
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.
- 5d ago First seen · 257 lines · 2,746 tokens per session scan A 2a9a86ae349d
teguma AGENTS.md is an instructions file published in the GitHub repository Doyajin174/teguma (0 stars, last pushed 28d ago), licensed MIT. It adds 2,746 tokens to every session, about $0.0137 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-31.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.