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 agentmods add skills/getlytos/lytos-cli/git-workflownpx skills add getlytos/lytos-cli --skill git-workflowgit clone --depth 1 https://github.com/getlytos/lytos-cliWhat 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 | $0.00046 | $0.02192 |
| Opus 5 | $0.00023 | $0.01096 |
| Sonnet 5 | $0.00009 | $0.00438 |
| Haiku 4.5 | $0.00005 | $0.00219 |
Grade A, and why
git-workflow 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 2d 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 — 298 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Skill — Git Workflow
This skill defines the Git conventions to follow on a project using Lytos. It covers branch naming, commit format, merge workflow, and collaboration rules. An agent loaded with this skill applies these conventions without deviation.
When to invoke this skill
- At each branch creation
- At each commit
- When opening a PR
- In case of conflict or question about the workflow
Workflow models — choose your fit
Lytos does not impose a single workflow. Choose the one that matches your project:
| Model | How it works | Best for |
|---|---|---|
| GitHub Flow | main + feature branches. Merge to main, deploy from main. |
Most projects, small teams, continuous deployment |
| Git Flow | main + dev + feature branches. Release branches for staging. |
Projects with scheduled releases, multiple environments |
| Trunk-Based | Everyone commits to main (or very short-lived branches). Feature flags for incomplete work. |
High-velocity teams, strong CI, DORA top performers |
The rest of this skill uses GitHub Flow as the default (main + feature branches). If your project uses Git Flow, add a dev branch as the PR target. If trunk-based, skip branches entirely and commit to main behind feature flags.
DORA research consistently shows: shorter-lived branches and faster integration correlate with higher team performance. When in doubt, prefer simpler workflows.
Branch naming convention
Format
type/ISS-XXXX-descriptive-slug
Branch types
| Type | Usage | Example |
|---|---|---|
feat |
New feature | feat/ISS-0012-add-cart |
fix |
Bug fix | fix/ISS-0034-login-error |
refactor |
Refactoring with no functional change | refactor/ISS-0045-extract-auth-service |
chore |
Technical task (config, deps, CI) | chore/ISS-0050-update-dependencies |
docs |
Documentation only | docs/ISS-0022-readme-payment-module |
test |
Adding or fixing tests | test/ISS-0028-unit-tests-tax-calculation |
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.
- 2d ago First seen · 298 lines · 46 tokens per session scan A b21d7c7b3c2f
git-workflow is a skill published in the GitHub repository getlytos/lytos-cli (2 stars, last pushed 2d ago), licensed MIT. It adds 46 tokens to every session and 2,192 once invoked, about $0.0002 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
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
brainstorming
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
auto-perf-optimize
Run agent-driven VS Code performance or memory investigations. Use when asked to launch Code OSS, automate a VS Code scenario, run the Chat memory smoke runner, capture renderer heap snapshots, take workflow screenshots, compare run summaries, or drive a repeatable scenario before heap-snapshot analysis.
chat-perf
Run chat perf benchmarks and memory leak checks against the local dev build or any published VS Code version. Use when investigating chat rendering regressions, validating perf-sensitive changes to chat UI, or checking for memory leaks in the chat response pipeline.
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…