asplos-related-work

asplos-related-work is a skill for Claude Code from brycewang-stanford/Awesome-Journal-Skills. It costs 72 tokens per session (1,516 once invoked), scanned A, original, MIT.

A guide to writing related work for an ASPLOS paper, a research paper in computer systems and software. It compares the work with architecture, operating-systems, compiler, accelerator, and earlier ASPLOS research while following citation and anonymous-review rules.

In plain words
What is it for?
Use it to map prior research, place your contribution against competing approaches, and check citations for full names, DOIs, your own work, and arXiv papers.
Why use it?
It prevents a paper from appearing unaware of important research in one of the communities that ASPLOS reviewers represent. It also reduces citation and anonymity mistakes.

Skill for Claude Code

Written for Claude Code: shipped in a Claude Code plugin.

Part of the asplos-skills plugin — 12 skills shipped together

Good fit Use it to map prior research, place your contribution against competing approaches, and check citations for full names, DOIs, your own work, and arXiv papers.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/brycewang-stanford/awesome-journal-skills/asplos-related-work
About the project

Awesome Journal Skills is a collection of agent skill packs tailored to hundreds of academic journals across fields including economics, social science, medicine, science, and engineering. Researchers use the packs for tasks such as choosing topics, designing empirical strategies, preparing tables and figures, submitting papers, and responding to reviewers. The catalogue entries are the project's journal-specific skills and related plugins.

brycewang-stanford/Awesome-Journal-Skills · 1,372 stars · on GitHub · copaper.ai

Install

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.

Any agent
npx skills add brycewang-stanford/Awesome-Journal-Skills --skill asplos-related-work
Clone the repo
git clone --depth 1 https://github.com/brycewang-stanford/Awesome-Journal-Skills

Made for: Claude Code.

Or install asplos-skills, the plugin that ships this one along with the rest of its 12 skills.

Wrote 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.

agentmods badge for asplos-related-work

README.md
[![agentmods](https://agentmods.dev/badge/skills/brycewang-stanford/awesome-journal-skills/asplos-related-work/github.svg)](https://agentmods.dev/skills/brycewang-stanford/awesome-journal-skills/asplos-related-work)
Your own site
<a href="https://agentmods.dev/skills/brycewang-stanford/awesome-journal-skills/asplos-related-work"><img src="https://agentmods.dev/badge/skills/brycewang-stanford/awesome-journal-skills/asplos-related-work/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.

agentmods 80×15 button for asplos-related-work

Your own site · 80×15
<a href="https://agentmods.dev/skills/brycewang-stanford/awesome-journal-skills/asplos-related-work"><img src="https://agentmods.dev/badge/skills/brycewang-stanford/awesome-journal-skills/asplos-related-work.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 72 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 1,516 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.
Origin original No closer match found in the catalogue.
Token cost

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.

ModelPer sessionOnce invoked
Fable 5.1 $0.00072 $0.01516
Opus 5.5 $0.00029 $0.00606
Sonnet 5.5 $0.00014 $0.00303
Haiku 4.5 $0.00007 $0.00152

Measured 1mo ago against content hash cc30467cf401, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

asplos-related-work 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.

ASPLOS-Skills/skills/asplos-related-work/SKILL.md · 124 lines

How it starts

The opening of the file, as written. The whole thing — 124 lines — stays where its author put it; the contents beside it link to each section on GitHub.

An ASPLOS reviewer pool is assembled from three communities, and each reviewer checks whether their literature is handled competently. Related work at this venue is therefore a coverage problem across parallel lanes — a paper positioned beautifully against the OS literature and blankly against the architecture literature reads as half-researched to half its reviewers.

The five lanes

Lane What must be shown Failure the lane's reviewers spot
Architecture (ISCA/MICRO/HPCA lineage) The hardware structure or mechanism is new relative to prior microarchitectural work Reinvented prefetcher/hint/metadata scheme under a new name
OS/systems (SOSP/OSDI/EuroSys/ATC lineage) The policy/runtime layer differs from existing kernel or hypervisor mechanisms "The kernel already does this with tunables"
PL/compilers (PLDI/POPL/CGO lineage) Language/compiler-level alternatives are acknowledged when the problem admits them Hardware solution to a problem the compiler community solved statically
Accelerator/domain (when applicable) Placement in the accelerator design space with honest technology normalization Comparing against a three-generation-old design point
Prior ASPLOS The intersection lineage itself — what earlier cross-layer attempts did Missing the exact ASPLOS paper a PC member wrote or shepherded

For the last lane, mine the venue's own memory: the ACM DL ASPLOS series and the Influential Paper Award list (see ../../resources/exemplars/library.md) identify the papers the community regards as canonical for a given boundary.

Differentiate on the boundary, not the components

The distinctive ASPLOS positioning move: prior work usually shares components with yours (a similar hardware structure, a similar kernel policy) while drawing the hardware/software boundary elsewhere. Say precisely where each prior system draws it and why yours moves it:

Template, per closest-prior system:
  "<System> provides <capability> at <layer>, which requires <cost/assumption>.
   Because it keeps <decision> in <layer>, it cannot <the thing your boundary
   placement enables>. We move <decision> to <layer>, which is what makes
   <headline property> possible."

Read the full file on GitHub · 124 lines

Changes

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.

  1. 1mo ago First seen · 124 lines · 72 tokens per session scan A cc30467cf401

Subscribe to this mod's changes

asplos-related-work is a skill published in the GitHub repository brycewang-stanford/Awesome-Journal-Skills (1,372 stars, last pushed 1mo ago), licensed MIT. It adds 72 tokens to every session and 1,516 once invoked, about $0.0003 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-15.

Related

asplos-related-work compared with skills from other repositories

asplos-related-work next to 6 skills from other repositories
ModTypeStarsLast pushLicenceScanTokensWorks with
asplos-related-workbrycewang-stanford/Awesome-Journal-SkillsSkill1.4k1mo agoMITA72Claude Code
alterlab-qiime2-ampliconAlterLab-IEU/AlterLab-Academic-SkillsSkill85yesterdayMITA270Claude Code
alterlab-paper-writerAlterLab-IEU/AlterLab-Academic-SkillsSkill85yesterdayMITA271Claude Code
alterlab-citation-verifierAlterLab-IEU/AlterLab-Academic-SkillsSkill85yesterdayMITA218Claude Code
alterlab-timesfmAlterLab-IEU/AlterLab-Academic-SkillsSkill85yesterdayMITA150Claude Code
fin-submit-checkcsmar432/finai-researchSkill1093d agoMITA37Claude Code, Codex
alterlab-phylogeneticsAlterLab-IEU/AlterLab-Academic-SkillsSkill85yesterdayMITA152Claude Code