Audit GitHub Actions that run AI agents for prompt injection, unsafe interpolation, sandbox gaps, and permissive actor rules. Use for agentic CI workflows, not general application code review.
日本語の概要は準備中です。原文の説明を表示しています。
Look up and read Hugging Face paper pages in markdown, and use the papers API for structured metadata such as authors, linked models/datasets/spaces, Github repo and project page. Use when the user shares a Hugging Face paper page URL, an arXiv URL or ID, or asks to summarize, explain, or analyze an AI research paper.
インストールする前に、エージェントに与えられる指示の中身を確認できます。
Hugging Face Paper pages (hf.co/papers) is a platform built on top of arXiv (arxiv.org), specifically for research papers in the field of artificial intelligence (AI) and computer science. Hugging Face users can submit their paper at hf.co/papers/submit, which features it on the Daily Papers feed (hf.co/papers). Each day, users can upvote papers and comment on papers. Each paper page allows authors to:
authors field). This makes the paper page appear on their Hugging Face profile.Whenever someone mentions a HF paper or arXiv abstract/PDF URL in a model card, dataset card or README of a Space repository, the paper will be automatically indexed. Note that not all papers indexed on Hugging Face are also submitted to daily papers. The latter is more a manner of promoting a research paper. Papers can only be submitted to daily papers up until 14 days after their publication date on arXiv.
The Hugging Face team has built an easy-to-use API to interact with paper pages. Content of the papers can be fetched as markdown, or structured metadata can be returned such as author names, linked models/datasets/spaces, linked Github repo and project page.
https://huggingface.co/papers/2602.08025)https://huggingface.co/papers/2602.08025.md)https://arxiv.org/abs/2602.08025 or https://arxiv.org/pdf/2602.08025)2602.08025)It's recommended to parse the paper ID (arXiv ID) from whatever the user provides:
| Input | Paper ID |
|---|---|
https://huggingface.co/papers/2602.08025 | 2602.08025 |
https://huggingface.co/papers/2602.08025.md | 2602.08025 |
https://arxiv.org/abs/2602.08025 | 2602.08025 |
https://arxiv.org/pdf/2602.08025 | 2602.08025 |
2602.08025v1 | 2602.08025v1 |
2602.08025 | 2602.08025 |
This allows you to provide the paper ID into any of the hub API endpoints mentioned below.
The content of a paper can be fetched as markdown like so:
curl -s "https://huggingface.co/papers/{PAPER_ID}.md"
This should return the Hugging Face paper page as markdown. This relies on the HTML version of the paper at https://arxiv.org/html/{PAPER_ID}.
There are 2 exceptions:
Alternatively, you can request markdown from the normal paper page URL, like so:
curl -s -H "Accept: text/markdown" "https://huggingface.co/papers/{PAPER_ID}"
All endpoints use the base URL https://huggingface.co.
Fetch the paper metadata as JSON using the Hugging Face REST API:
curl -s "https://huggingface.co/api/papers/{PAPER_ID}"
This returns structured metadata that can include:
To find models linked to the paper, use:
curl https://huggingface.co/api/models?filter=arxiv:{PAPER_ID}
To find datasets linked to the paper, use:
curl https://huggingface.co/api/datasets?filter=arxiv:{PAPER_ID}
To find spaces linked to the paper, use:
curl https://huggingface.co/api/spaces?filter=arxiv:{PAPER_ID}
Claim authorship of a paper for a Hugging Face user:
curl "https://huggingface.co/api/settings/papers/claim" \
--request POST \
--header "Content-Type: application/json" \
--header "Authorization: Bearer $HF_TOKEN" \
--data '{
"paperId": "{PAPER_ID}",
"claimAuthorId": "{AUTHOR_ENTRY_ID}",
"targetUserId": "{USER_ID}"
}'
POST /api/settings/papers/claimpaperId (string, required): arXiv paper identifier being claimedclaimAuthorId (string): author entry on the paper being claimed, 24-char hex IDtargetUserId (string): HF user who should receive the claim, 24-char hex IDFetch the Daily Papers feed:
curl -s -H "Authorization: Bearer $HF_TOKEN" \
"https://huggingface.co/api/daily_papers?p=0&limit=20&date=2017-07-21&sort=publishedAt"
GET /api/daily_papersp (integer): page numberlimit (integer): number of results, between 1 and 100date (string): RFC 3339 full-date, for example 2017-07-21week (string): ISO week, for example 2024-W03month (string): month value, for example 2024-01submitter (string): filter by submittersort (enum): publishedAt or trendingList arXiv papers sorted by published date:
curl -s -H "Authorization: Bearer $HF_TOKEN" \
"https://huggingface.co/api/papers?cursor={CURSOR}&limit=20"
GET /api/paperscursor (string): pagination cursorlimit (integer): page size, 1-100 (same bounds as the daily-papers endpoint above)Perform hybrid semantic and full-text search on papers:
curl -s -H "Authorization: Bearer $HF_TOKEN" \
"https://huggingface.co/api/papers/search?q=vision+language&limit=20"
This searches over the paper title, authors, and content.
GET /api/papers/searchq (string): search query, max length 250limit (integer): number of results, between 1 and 120Insert a paper from arXiv by ID. If the paper is already indexed, only its authors can re-index it:
curl "https://huggingface.co/api/papers/index" \
--request POST \
--header "Content-Type: application/json" \
--header "Authorization: Bearer $HF_TOKEN" \
--data '{
"arxivId": "{ARXIV_ID}"
}'
POST /api/papers/indexarxivId (string, required): arXiv ID to index, for example 2301.00001^\d{4}\.\d{4,5}$Update the project page, GitHub repository, or submitting organization for a paper. The requester must be the paper author, the Daily Papers submitter, or a papers admin:
curl "https://huggingface.co/api/papers/{PAPER_OBJECT_ID}/links" \
--request POST \
--header "Content-Type: application/json" \
--header "Authorization: Bearer $HF_TOKEN" \
--data '{
"projectPage": "https://example.com",
"githubRepo": "https://github.com/org/repo",
"organizationId": "{ORGANIZATION_ID}"
}'
POST /api/papers/{paperId}/linkspaperId (string, required): Hugging Face paper object IDgithubRepo (string, nullable): GitHub repository URLorganizationId (string, nullable): organization ID, 24-char hex IDprojectPage (string, nullable): project page URLhttps://huggingface.co/papers/{PAPER_ID} or md endpoint: the paper is not indexed on Hugging Face paper pages yet./api/papers/{PAPER_ID}: the paper may not be indexed on Hugging Face paper pages yet.If the Hugging Face paper page does not contain enough detail for the user's question:
https://huggingface.co/papers/{PAPER_ID}https://arxiv.org/abs/{PAPER_ID}https://arxiv.org/pdf/{PAPER_ID}Authorization: Bearer $HF_TOKEN..md endpoint for reliable machine-readable output./api/papers/{PAPER_ID} when you need structured JSON fields instead of page markdown.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Audit GitHub Actions that run AI agents for prompt injection, unsafe interpolation, sandbox gaps, and permissive actor rules. Use for agentic CI workflows, not general application code review.
日本語の概要は準備中です。原文の説明を表示しています。
Audit and improve project-rules files (AGENTS.md, CLAUDE.md, .agents/instructions, local overrides) so the agent keeps accurate project context. Use when the user asks to check, audit, review, update, improve, or fix their AGENTS.md or CLAUDE.md, mentions "project rules maintenance" or "agent context optimization", or when the codebase has changed enough that the rules file may be stale. Scans the repository for every rules file, grades each against a quality rubric, outputs a quality report, and applies targeted edits only after user approval.
日本語の概要は準備中です。原文の説明を表示しています。
Capture learnings from the current session into the project-rules file (AGENTS.md, CLAUDE.md, or local override) so future sessions benefit. Use when the user says "revise the rules", "update AGENTS.md / CLAUDE.md with what we just learned", "save this to project memory", "remember this for next time", or at the end of a productive session when valuable context has emerged that is not yet documented. This complements agents-md-improver — improver audits, while this one captures.
日本語の概要は準備中です。原文の説明を表示しています。
Operational rubric that turns "don't make AI slop" into observable properties, severity levels, evidence requirements, and repair actions for interface design. Use as the reference rubric when building or reviewing marketing sites, product interfaces, dashboards, portfolios, or e-commerce pages, especially alongside frontend-design.
日本語の概要は準備中です。原文の説明を表示しています。
Design a feature architecture by analyzing existing codebase patterns and conventions, then provide a comprehensive implementation blueprint with specific files to create or modify, component designs, data flows, and a build sequence. Use this skill when the user asks for an architecture design, an implementation plan for a non-trivial feature, or when dispatched as a sub-task during feature-dev architecture phase.
日本語の概要は準備中です。原文の説明を表示しています。
Deeply analyze an existing codebase feature by tracing execution paths, mapping architecture layers, understanding patterns and abstractions, and documenting dependencies. Use this skill when you need to understand how a feature works before modifying or extending it, when dispatched as a sub-task during feature-dev exploration, or when the user asks "how does X work in this codebase".
日本語の概要は準備中です。原文の説明を表示しています。