Agentero is a local research workspace that connects papers, structured reading material, Markdown notes, and AI agents in one place. Researchers use it to read and annotate PDFs, extract formulas and figures, organize literature, and collaborate with agents on research tasks while keeping context locally. Its catalogue skills and instruction support agent-assisted research workflows in Agentero.
Borrowing it
Nothing to install: this file belongs to poco-ai/Agentero. 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/poco-ai/Agentero/main/.agents/skills/commit/SKILL.mdgit clone --depth 1 https://github.com/poco-ai/AgenteroWrote 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/poco-ai/agentero/commit)<a href="https://agentmods.dev/skills/poco-ai/agentero/commit"><img src="https://agentmods.dev/badge/skills/poco-ai/agentero/commit/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/poco-ai/agentero/commit"><img src="https://agentmods.dev/badge/skills/poco-ai/agentero/commit.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector warn
SkillSpector: 1 finding, up to high
These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →
- high Tool Misuse · line 14 Tool parameters are crafted to achieve unintended or unsafe behavior. Parameter abuse can bypass intended safety checks (e.g. shell=True, --force, dangerous glob patterns).Fix: Validate all tool parameters against an allowlist. Reject dangerous parameter values (shell=True, --force, -rf /) and use safe defaults.
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.00024 | $0.00483 |
| Opus 5.5 | $0.00010 | $0.00193 |
| Sonnet 5.5 | $0.00005 | $0.00097 |
| Haiku 4.5 | $0.00002 | $0.00048 |
Grade A, and why
commit 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
Local Commits
把当前工作区的改动按逻辑拆分为多个本地 Git commit，并保持每个 commit 可理解、可审查、可回滚。
执行规则
- 先读取
git status、未暂存 diff、已暂存 diff 和最近提交历史。保留用户已有改动，不使用git reset --hard、git checkout --或其他破坏性操作。 - 按独立目的分组改动，例如功能代码、测试、文档、版本 bump、CI；不要仅按文件夹机械分组。
- 每组提交前检查相关文档：修改 UI、数据契约、发布流程或 Vault 语义时，把对应文档放入同一逻辑变更或单独的文档 commit。
- 每个 commit 只包含一个目的，使用符合 Conventional Commits 的标题，例如
feat: ...、fix: ...、docs: ...、chore(release): bump version to ...。 - 使用明确的文件路径或交互式 patch 精确暂存，避免把无关改动带入 commit；不要依赖
git add .盲目提交。 - 每组提交前运行与该组风险匹配的最小验证；版本 bump 至少检查所有版本字段和
Cargo.lock，代码改动至少运行对应类型检查、测试或 lint。 - 提交后检查
git log和git status，确认 commit 顺序、标题、内容归属和剩余未提交改动都正确。 - 默认只创建本地 commit，不 amend、rebase、创建 tag、push 或发布 Release；这些操作必须由用户明确要求。
异常处理
- 如果改动无法合理拆分，先说明分组方案再提交。
- 如果存在冲突、敏感文件、生成物或无法解释的改动，停止提交相关部分并报告路径与原因。
- 不为无关的已有改动补写说明、不重写用户提交历史。
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 · 28 lines · 24 tokens per session scan A 703bfc65405d
commit is a skill published in the GitHub repository poco-ai/Agentero (1,032 stars, last pushed today), licensed MIT. It adds 24 tokens to every session and 483 once invoked, about $0.0001 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-08-30.
Other skills, from other repositories
open-code-review
Performs AI-powered code review on Git changes using the ocr CLI from alibaba/open-code-review. Use when the user asks to review code, review a pull request, review staged/unstaged changes, review a commit, or compare branches for code quality issues. Produces line-level review comments and can automatically apply…
baby-sit
Monitor a GitHub pull request until CI is green, diagnose failures, and rerun only evidence-backed flaky GitHub Actions jobs.
git-checkpoint
Use git as a safety net - create a checkpoint commit before risky or large changes and roll back cleanly if a change makes things worse. Use before multi-file refactors.
csv
CSV data processing — view, filter, convert, merge tabular data. Zero barrier — use with x-cmd, Python, or awk. Use for "csv", "data", "table", "spreadsheet", "conversion".
git
Git and code hosting platform management — GitHub, GitLab, Codeberg, Forgejo. Zero barrier — install x-cmd and manage repos from the terminal. Use for "git", "github", "gitlab", "repo", "pull request", "code hosting".
meta-codereview-current-diff
Read the current uncommitted diff, run three independent reviewers (safety + tests-coverage + style) in parallel, then arbitrate a single BLOCK / BLOCKWITHOVERRIDE / PASSWITHNOTES verdict. Use before commit when you want a multi-perspective second-opinion instead of a single-reviewer agent loop.