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 neuromechanist/research-skills --skill project-preflightgit clone --depth 1 https://github.com/neuromechanist/research-skillsWrote 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/neuromechanist/research-skills/project-preflight)<a href="https://agentmods.dev/skills/neuromechanist/research-skills/project-preflight"><img src="https://agentmods.dev/badge/skills/neuromechanist/research-skills/project-preflight/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/neuromechanist/research-skills/project-preflight"><img src="https://agentmods.dev/badge/skills/neuromechanist/research-skills/project-preflight.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.00047 | $0.00338 |
| Opus 5.5 | $0.00019 | $0.00135 |
| Sonnet 5.5 | $0.00009 | $0.00068 |
| Haiku 4.5 | $0.00005 | $0.00034 |
Grade A, and why
project-preflight 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 1mo 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
Project Preflight
Run the bundled read-only preflight probe before relying on repository, shell, terminal, GitHub, or native-agent state. It never spawns agents, changes files, or prints credentials.
Resolve the executable from the project plugin installation that contains this
skill, using its sibling bin/project-preflight path. When working from a
checkout, that path is plugins/project/bin/project-preflight. Invoke the
executable by its absolute path rather than assuming that the plugin's bin/
directory is on PATH:
<project-plugin-root>/bin/project-preflight --format json
Use the JSON fields to distinguish repository-detection failures from optional
GitHub or native-agent capability failures. Required repository fields are
repo_root, integration_branch, and current_branch. Before a GitHub
operation, inspect has_gh, gh_command_status, gh_network_status,
gh_auth_status, gh_token_status, and gh_child_credential_status; before a
review panel, inspect native_agent_status, native_agent_surface,
agent_model, agent_effort, and agent_max_reviewers.
If the executable cannot be resolved, report that the project plugin is partially installed instead of substituting a different detector or inferring missing values.
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.
- 1mo ago First seen · 34 lines · 47 tokens per session scan A 992061531cc6
project-preflight is a skill published in the GitHub repository neuromechanist/research-skills (49 stars, last pushed yesterday), licensed BSD-3-Clause. It adds 47 tokens to every session and 338 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-22.
Other skills, from other repositories
godot-debugging
Use when debugging Godot projects — remote debugger, print techniques, signal tracing, common error patterns and fixes.
beehave
Use when using the Beehave addon — pure-GDScript behavior trees with composites, decorators, leaves, a blackboard, and a visual runtime debugger.
michel-monitor-pull-request-github-actions
Diagnose a failed, stuck, or never-triggered CI run on a GitHub PR, apply a local fix if possible, push it, and document the result in a single running PR comment. Invoke whenever Michel's CI monitor loop triggers with anyfailure, stuck, or nottriggered — the bash loop already handles pending and allgreen silently, so…
releasing-godot-prompter
Use when cutting a GodotPrompter release or bumping its version — the version-bump sequence, tag-triggered workflow, and the marketplace manifests that must follow.
git-mastery
Advanced Git: rebase, bisect, reflog, cherry-pick, worktrees, LFS. Triggers: rebase, bisect, cherry-pick, reflog, force push, merge conflict, worktree.
github-readme
Generate polished GitHub README.md files for Mick's repositories in his established voice and structure. Always trigger immediately when the user's message starts with "readme" or "gr". Also trigger on "write a readme", "generate readme", "readme for this repo", "document this repo", or any request to create or…