Borrowing it
Nothing to install: this file belongs to Foxfire1st/agents-remember. 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/Foxfire1st/agents-remember/main/.agents/skills/c-05-create-or-update-onboarding-files/SKILL.mdgit clone --depth 1 https://github.com/Foxfire1st/agents-rememberWrote 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/foxfire1st/agents-remember/c-05-create-or-update-onboarding-files)<a href="https://agentmods.dev/skills/foxfire1st/agents-remember/c-05-create-or-update-onboarding-files"><img src="https://agentmods.dev/badge/skills/foxfire1st/agents-remember/c-05-create-or-update-onboarding-files/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/foxfire1st/agents-remember/c-05-create-or-update-onboarding-files"><img src="https://agentmods.dev/badge/skills/foxfire1st/agents-remember/c-05-create-or-update-onboarding-files.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.00067 | $0.04088 |
| Opus 5 | $0.00034 | $0.02044 |
| Sonnet 5 | $0.00013 | $0.00818 |
| Haiku 4.5 | $0.00007 | $0.00409 |
Grade A, and why
c-05-create-or-update-onboarding-files 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 11d 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 — 232 lines — stays where its author put it; the contents beside it link to each section on GitHub.
c-05-create-or-update-onboarding-files Create Or Update Onboarding Files
This package owns durable onboarding maintenance for two artifact types and one storage-specific adapter layer:
- file-level onboarding units for concrete source files
- repo-level entity catalogs for load-bearing cross-layer entities
Inline onboarding does not replace the file-level content model. It reuses the same semantic sections and adds storage-specific syntax, placement, and digest rules through the inline adapter workflow/template.
Planning stays in task artifacts. This package defines how onboarding itself is created, updated, and kept structurally consistent.
Before maintaining onboarding, use c-08-ar-coordination-context-resolver to resolve the target repository's active coordination context. It must use the Domain Documentation category declared in the resolved system/sources.md for the onboarding slice being maintained, rather than assuming that adjacent onboarding alone is sufficient or hard-coding one particular documentation system into the skill.
Seat routing: in the manager -> builder -> reviewer -> curator chain (l-01-agent-lifecycles
roles/curator.md), onboarding create/update duty during leaf work belongs to the curator seat, not
the builder — the builder produces code and a turn report only. The curator runs this skill's
workflows from a change set (landed diff), the leaf task doc, and notes/ fed to it by the manager,
and routes each item to the right onboarding home (a concrete sidecar or the governing overview
whose subject it is; the L3 Operational-Notes target is last-resort only, never a default). The
strict 1-to-1 source mapping, governing-overview links, and metadata rules below are unchanged by
this routing — only the writing seat moved. A solo flat session with no separate curator seat runs
this skill itself, exactly as before.
When onboarding maintenance is happening inside a c-09-git-worktree-manager
worktree, check worktree_status before starting memory entries. If its
freshness block reports that the recorded code or memory source branch moved,
run worktree_sync before writing onboarding content unless that sync is blocked
by conflicts or an explicit developer decision. Carrying the moved official line
first keeps later onboarding updates and ledger rows on top of current source
history instead of forcing a conflict-heavy carryover after the task is otherwise
done.
The c-05-create-or-update-onboarding-files skill remains the normal public entry point for create or update onboarding requests. When the request is route-level slice creation, refresh, move handling, or deletion cleanup, the c-05-create-or-update-onboarding-files skill should route the work to the c-03-repo-bootstrap skill existing-memory-slice-maintenance mode instead of reducing it to unrelated file-level updates.
What ships with it
6 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.
- 11d ago First seen · 232 lines · 67 tokens per session scan A 64a37ade1a9e
c-05-create-or-update-onboarding-files is a skill published in the GitHub repository Foxfire1st/agents-remember (27 stars, last pushed 2d ago), licensed MIT. It adds 67 tokens to every session and 4,088 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-30.
Other skills, from other repositories
foundry-hosted-agent-validation
Step-by-step process for validating a Python Foundry hosted agent sample (under python/samples/04-hosting/foundry-hosted-agents/) end to end — running it locally (native runtime and azd ai agent run) and after deploying it to an Azure AI Foundry project with azd. Use this when asked to validate a hosted agent sample.
python-feature-lifecycle
Guidance for package and feature lifecycle in the Agent Framework Python codebase, including stage meanings, feature-stage decorators, feature enums, and how to move APIs from one stage to the next.
python-development
Coding standards, conventions, and patterns for developing Python code in the Agent Framework repository. Use this when writing or modifying Python source files in the python/ directory.
foundry-config-setup
Resolve missing setup caused by a hardcoded Foundry project endpoint or model in a sample. Use when a sample fails because it uses a placeholder/hardcoded projectendpoint (for example "https://your-project.services.ai.azure.com") or a hardcoded model instead of reading them from the environment.
trigger-authoring-tasks
Covers writing backend Trigger.dev tasks with @trigger.dev/sdk: defining task() and schemaTask(), the run function and its ctx, retries, waits, queues and concurrency, idempotency keys, run metadata, logging, triggering other tasks (and the Result shape), scheduled/cron tasks, and the essentials of trigger.config.ts.…
background
Use when the user wants to see, inspect, cancel, or prune background agents fired during prior chain runs. Read/manage .hyperflow/background/registry.json and the per-agent output buffers at .hyperflow/background/ .md. Standalone — never auto-invoked. Trigger with /hyperflow:background, "list background agents"…