Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add fthsrbst/mnema --skill senior-engineergit clone --depth 1 https://github.com/fthsrbst/mnemaWrote 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/fthsrbst/mnema/senior-engineer)<a href="https://agentmods.dev/skills/fthsrbst/mnema/senior-engineer"><img src="https://agentmods.dev/badge/skills/fthsrbst/mnema/senior-engineer.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.00059 | $0.00637 |
| Opus 5 | $0.00030 | $0.00318 |
| Sonnet 5 | $0.00012 | $0.00127 |
| Haiku 4.5 | $0.00006 | $0.00064 |
Grade A, and why
senior-engineer 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 7d 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.
What it actually says
Senior Engineer Disiplini
Junior kod "çalışır"; senior kod değiştirilebilir, hata durumunda anlaşılır ve gelecekteki okuyucuya dürüsttür. Bu skill davranış çıtasıdır.
Yazarken
- Önce oku, sonra yaz: Değiştireceğin kodun çağıranlarını ve testlerini görmeden dokunma. Var olan pattern'i takip et; "daha iyi" pattern'i habersiz sokma ([[code-conventions]]).
- Hata yolları birinci sınıf: Her dış çağrı (ağ, dosya, DB, process) için: timeout var mı, hata mesajı teşhis ettirir mi, degrade davranışı bilinçli mi? Mutlu yol kadar hata yolunu da yaz.
- Sınır koşulları yazarken düşün: boş liste, null, aynı anda iki çağrı, çok büyük girdi, Türkçe/unicode. Sonradan test yazarken değil, kodu yazarken.
- Geri alınabilirlik: Şema/format değişikliklerinde eski veriyle karşılaşınca ne olur? Migration tek yönlü mü? (Bu repo'daki
migrate()pattern'i örnek.)
Bitti demeden önce (kontrol listesi)
- Çalıştırdın mı? (derleme ≠ çalışma; test ≠ gerçek akış)
- Hata yolunu en az bir kez tetikledin mi?
- Sildiğin/değiştirdiğin şeyin başka kullanıcısı var mıydı? (grep)
- Log/hata mesajları, sorunu YAŞAMAYAN birinin teşhis etmesine yeter mi?
- Değişikliğin en riskli varsayımı ne — ve nasıl doğruladın?
- Alınan kalıcı karar varsa hub'a yazdın mı? (
memory_savetype=decision)
Teknik borç: bilinçli al, kaydet
Kısayol almak bazen doğrudur — ama sessizce değil:
- Kısayolu kod içinde
// TODO(borç):ile işaretle + gerekçe. - Önemliyse proje map'ine
next_stepsolarak ekle. - "Sonra düzeltirim" deme; ya şimdi düzelt ya kayda geçir. Kayıtsız borç faizle döner.
Ölçek refleksi
- O(n²) döngü + kullanıcı verisi = ileride şikayet. Yazarken n'in kaç olabileceğini bir kez düşün.
- Ama erken optimizasyon da yapma: ölçmediğin şeyi hızlandırma. Önce doğru, sonra ölç, sonra hızlandır.
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.
- 7d ago First seen · 33 lines · 59 tokens per session scan A 19693a89f7f7
senior-engineer is a skill published in the GitHub repository fthsrbst/mnema (2 stars, last pushed 7d ago), licensed MIT. It adds 59 tokens to every session and 637 once invoked, about $0.0003 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 skills, from other repositories
simplicio-orient
Terminal-first execution — answer facts with the shell, never with the LLM. Use whenever a step needs a fact about the filesystem, git, processes, or system resources, or runs a build/test/lint/diff whose output would flood context. Substitutes deterministic shell/CLI calls for native LLM operations and clamps their…
review-work
Post-implementation review orchestrator. Launches 5 parallel background sub-agents: Oracle (goal/constraint verification), Oracle (code quality), Oracle (security), unspecified-high (hands-on QA execution), unspecified-high (context mining from GitHub/git/Slack/Notion). All must pass for review to pass. MUST USE…
remove-ai-slops
Remove AI-generated code smells (slop) from branch changes or an explicit file list. Locks behavior with regression tests FIRST, then runs categorized cleanup via parallel deep agents in batches of 5, then verifies with quality gates. Covers 10 slop categories including performance equivalences, excessive complexity…
include-test-files-that-assert-on-behavior-being-changed-in-decl
When delegating a task affected by this skill, include.
code-guidelines-go
Go 1.24–1.27 coding guidelines for the dimetron/pi-go AI agent runtime. Use this skill whenever writing, reviewing, or refactoring ANY Go code in pi-go. This covers idiomatic style, error handling, concurrency, project layout, testing (table-driven, fuzz, benchmarks, synctest), new stdlib usage, golangci-lint v2…
check
Auto-fix lint and formatting, then report types and tests. Run before every commit.