Borrowing it
Nothing to install: this file belongs to vladm3105/aidoc-flow-framework. 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/vladm3105/aidoc-flow-framework/dev/.agents/skills/start-session/SKILL.mdgit clone --depth 1 https://github.com/vladm3105/aidoc-flow-frameworkWrote 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/vladm3105/aidoc-flow-framework/start-session)<a href="https://agentmods.dev/skills/vladm3105/aidoc-flow-framework/start-session"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/start-session/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/vladm3105/aidoc-flow-framework/start-session"><img src="https://agentmods.dev/badge/skills/vladm3105/aidoc-flow-framework/start-session.svg" alt="Reviewed on agentmods" width="80" 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.00050 | $0.01019 |
| Opus 5.5 | $0.00020 | $0.00408 |
| Sonnet 5.5 | $0.00010 | $0.00204 |
| Haiku 4.5 | $0.00005 | $0.00102 |
Grade A, and why
start-session 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 10d 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 — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Start session
A handoff records the previous session's belief before its last actions settled. Treat it as a lead and reconstruct current state before choosing work.
1. Read the repository declaration
Open the active repository's AGENTS.md chain (falling back to CLAUDE.md where
the repo has not migrated yet) and determine its declared:
- handoff surface, if any;
- task tracker and in-progress mechanism;
- merge and release state sources;
- authorization for issue, project, or other external writes.
Do not invent a GitHub handoff for a file-based repository, or a file handoff for a tracker-based repository. If no handoff is declared, use recent commits, open issues, and open PRs and say that the state was derived.
2. Read without inheriting
For a file handoff, read the declared file. For a tracker handoff, identify the single current item using the repository's label or query. Zero open handoffs is not automatically an error: inspect the most recent closed or superseded item and current in-progress work before concluding state is missing.
Extract claims, not conclusions:
- what supposedly shipped;
- what remains in progress;
- blockers and their clearing conditions;
- the proposed next task;
- assumptions explicitly marked unverified.
3. Re-verify current state
Use primary evidence:
git status --short
git log --oneline -5
gh pr list --state open --limit 20 # when GitHub is the declared tracker
gh issue list --state open --limit 50
Check relevant PR state, merge commit, deployed version, tests, and cited files as needed. Distinguish merged from deployed. Record contradictions between the handoff and current evidence.
3.1 Verify Platform Technology Stack and Security Readiness
Verify that the task scope and tools align strictly with the Authoritative Platform Technology Stack (/home/ya/devd/technology_stack, specs 00–23):
- Approved Tech Stack: Confirm required runtimes, databases, and tooling exist in the approved stack.
- Prohibition of Insecure Options: Confirm no insecure options (e.g. plaintext secrets, disabled sandboxing, relaxed permissions, bypassed checks) are contemplated or used.
- Missing Tools Protocol: If needed tools are missing from the approved stack, explicitly inform the operator and request instructions before proceeding with implementation.
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.
- 10d ago Changed · +7 lines e676c1a10584
- 1mo ago First seen · 107 lines · 50 tokens per session scan A 1fdb5905023e
start-session is a skill published in the GitHub repository vladm3105/aidoc-flow-framework (17 stars, last pushed yesterday), licensed MIT. It adds 50 tokens to every session and 1,019 once invoked, about $0.0002 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-09-28.
Other skills, from other repositories
antfu-issue-triage
Triage open issues and PRs of the current GitHub repo - find already-fixed, duplicate, and spam items, suggest labels, gauge demand from reactions and comments, then present a table of proposed actions and comments for confirmation before touching anything. Use when asked to triage, organize, clean up, or groom issues…
mcore-split-pr
Split a PR into multiple PRs to reduce the number of required CODEOWNERS reviewer groups.
engineer-bot-ops
A workflow for carrying an engineering task from scope through implementation and reviewable delivery. It works with a repository's branch, existing changes, rules, checks, and permissions while separating completed, unverified, and next-step work.
shiplog
Recap of everything shipped since the last run - cross-repo PRs, security fixes, star deltas, and X traction, synthesized into a digest article and a ready-to-post shiplog in your voice.
llxprt-issue-workflow
Use this skill when asked to address, fix, or work on a GitHub issue in the llxprt-code repository. Covers the complete issue lifecycle - branch setup, gh CLI usage, test-first planning, subagent delegation and review loops, the full verification cycle (including the zai-glm-flash smoke test), open code review (ocr)…
connect
Choose which wiki this session uses, the team project's pages on the Nimbalyst server or the project's local wiki of files, and connect a repository to its team project. Use at the start of a task before any wiki tool, when a wiki tool returns reponotbound, ambiguousproject, pinmismatch, projectnotaccessible…